BorlandTalk.com Forum Index BorlandTalk.com
Borland discussion newsgroups
 
Archives   FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Importing the type library

 
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> Delphi Databases (ADO)
View previous topic :: View next topic  
Author Message
Richard Bibby
Guest





PostPosted: Fri Feb 20, 2004 10:08 am    Post subject: Importing the type library Reply with quote



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





PostPosted: Sat Feb 21, 2004 9:52 am    Post subject: Re: Importing the type library Reply with quote



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





PostPosted: Mon Feb 23, 2004 9:33 am    Post subject: Re: Importing the type library Reply with quote



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





PostPosted: Mon Feb 23, 2004 5:33 pm    Post subject: Re: Importing the type library Reply with quote

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
Display posts from previous:   
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> Delphi Databases (ADO) All times are GMT
Page 1 of 1

 
Jump to:  
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


Powered by phpBB © 2001, 2006 phpBB Group
SEO toolkit © 2004-2006 webmedic.