 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Richard Bibby Guest
|
Posted: Fri Feb 20, 2004 10:08 am Post subject: Importing the type library |
|
|
Hello,
When i am about import the Microsoft Active Data Object library into my
project i see that there are six versions of the library, from 2.0 up to
2.7.
Which version should i use and how do i know that when i deploy my
application that the client has the same version?
I noticed that you can not import different versions for different projects
because by default Delphi suggests the Imports directory, where i already
have imported the library for another project. Should i keep seperate
copies of my type libraries with each project, or should i always use the
same (and perhaps latest) version?
/Richard
|
|
| Back to top |
|
 |
Jeremy Collins Guest
|
Posted: Sat Feb 21, 2004 9:52 am Post subject: Re: Importing the type library |
|
|
Brian Bushay TeamB wrote:
| Quote: | Which version should i use and how do i know that when i deploy my
application that the client has the same version?
I noticed that you can not import different versions for different projects
because by default Delphi suggests the Imports directory, where i already
have imported the library for another project. Should i keep seperate
copies of my type libraries with each project, or should i always use the
same (and perhaps latest) version?
You want to use the lowest version that you expect your users will have.
|
Really? Why? I always use the latest version for development,
and deployment on older versions has never been a problem. Most
MDAC point releases are just bugfixes aren't they?
--
jc
Remove the -not from email
|
|
| Back to top |
|
 |
Richard Bibby Guest
|
Posted: Mon Feb 23, 2004 9:33 am Post subject: Re: Importing the type library |
|
|
Hej,
Thanks for the reply.
If I took for example 2.5, can i make sure that the customer has that during
installation? and delivery the correct dll if they do not?
/Richard
"Brian Bushay TeamB" <BBushay (AT) Nmpls (DOT) com> skrev i meddelandet
news:lmjd30hp1mpltrtau3gqkmqori9k7cggqb (AT) 4ax (DOT) com...
| Quote: |
Which version should i use and how do i know that when i deploy my
application that the client has the same version?
I noticed that you can not import different versions for different
projects
because by default Delphi suggests the Imports directory, where i already
have imported the library for another project. Should i keep seperate
copies of my type libraries with each project, or should i always use the
same (and perhaps latest) version?
You want to use the lowest version that you expect your users will have.
The lowest version of Mdac that Borland's ADO components are compatible
with is
2.1
--
Brian Bushay (TeamB)
[email]Bbushay (AT) NMPLS (DOT) com[/email]
|
|
|
| Back to top |
|
 |
Víctor Hugo Ulloa Melénde Guest
|
Posted: Mon Feb 23, 2004 5:33 pm Post subject: Re: Importing the type library |
|
|
Richard:
Remember there are compatibility considerations: for example, to use
XML when saving a recordset to a file, you must use MSDAC 2.6 at
least. There are other areas of concern, too. So, you must be
carefull selecting:
A. The features you need.
B. The version your clients will have installed.
On Fri, 20 Feb 2004 11:08:38 +0100, "Richard Bibby"
<richard.bibby (AT) profdoc (DOT) se> wrote:
| Quote: | Hello,
88878888
When i am about import the Microsoft Active Data Object library into my
project i see that there are six versions of the library, from 2.0 up to
2.7.
Which version should i use and how do i know that when i deploy my
application that the client has the same version?
I noticed that you can not import different versions for different projects
because by default Delphi suggests the Imports directory, where i already
have imported the library for another project. Should i keep seperate
copies of my type libraries with each project, or should i always use the
same (and perhaps latest) version?
/Richard
|
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|