Hi Guys,
I have a ready made Marketing Database.mdb application developed in Access2000 which some features are linking or working with
MsExcel2K (Export/Import Data), MsWord2K (Mail Merge in Envelops, Labels and snail mail) and MsOutlook2K (Sending Bulk Plain or HTML
Email).

My doubt is, our new client is fully working in XP Environment (OS & Office). Can any one tell or break-down to me any/all
possible
problem I will face installing my 2K.mdb to the above environment? If you can provide solution also, please do...

Any tips and help is highly appreciated..

TIA,
George

P.S. (Reversed)
If I will upgrade my 2K.mdb to XP, is there any possible problem I will face if I will install it in 2000 Environment?

George,

<< Can any one tell or break-down to me any/all possible
problem I will face installing my 2K.mdb to the above environment? If you 
can provide solution also, please do... >>

The only problem I consistently came across converting from Access 2.0 to 
Access '97 and then Access '97 to Access XP was calls to the reference 
libraries.

Microsoft has a habit of wanting people to update how they use and call 
libraries (which is good), but they have a nasty habit of doing it by 
turning OFF older libraries even though your previously existing databases 
survive on them (which is bad).  The result is that upon conversion your 
old databases fail miserably.  Whereas it's good that they're encouraging 
you to update your style of programming, it's inconceivable that you're 
going to waste valuable work time converting code in your older, already 
fine, "if it ain't broke don't fix it" databases.

To avoid this problem, open any module and click TOOLS | REFERENCES.  Make 
sure "Microsoft DAO 3.6 Object Library" is checked and high up on the 
list.  Also uncheck all those that are now labeled "MISSING" and find 
suitable replacements for them.

Also note:  The default version that Access XP saves databases is in 
Access 2000 format.  To change this, click TOOLS | OPTIONS, select 
the "Advanced" tab, and choose "Access 2002" for default file format.

Greg

Compared to the 97-2000 change, you will have very few if any problems.

-----Original Message-----
From: Gregory Serrano [mailto:SerranoG@m...]
Sent: Tuesday, November 19, 2002 7:22 AM
To: Access
Subject: [access] Re: Access2000 To XP


George,

<< Can any one tell or break-down to me any/all possible
problem I will face installing my 2K.mdb to the above environment? If you 
can provide solution also, please do... >>

The only problem I consistently came across converting from Access 2.0 to 
Access '97 and then Access '97 to Access XP was calls to the reference 
libraries.

Microsoft has a habit of wanting people to update how they use and call 
libraries (which is good), but they have a nasty habit of doing it by 
turning OFF older libraries even though your previously existing databases 
survive on them (which is bad).  The result is that upon conversion your 
old databases fail miserably.  Whereas it's good that they're encouraging 
you to update your style of programming, it's inconceivable that you're 
going to waste valuable work time converting code in your older, already 
fine, "if it ain't broke don't fix it" databases.

To avoid this problem, open any module and click TOOLS | REFERENCES.  Make 
sure "Microsoft DAO 3.6 Object Library" is checked and high up on the 
list.  Also uncheck all those that are now labeled "MISSING" and find 
suitable replacements for them.

Also note:  The default version that Access XP saves databases is in 
Access 2000 format.  To change this, click TOOLS | OPTIONS, select 
the "Advanced" tab, and choose "Access 2002" for default file format.

Greg

Thank for the nice tips Greg...

Cheers,
George


-----Original Message-----
From: Gregory Serrano [mailto:SerranoG@m...]
Sent: Tuesday, November 19, 2002 1:22 PM
To: Access
Subject: [access] Re: Access2000 To XP


George,

<< Can any one tell or break-down to me any/all possible
problem I will face installing my 2K.mdb to the above environment? If you 
can provide solution also, please do... >>

The only problem I consistently came across converting from Access 2.0 to 
Access '97 and then Access '97 to Access XP was calls to the reference 
libraries.

Microsoft has a habit of wanting people to update how they use and call 
libraries (which is good), but they have a nasty habit of doing it by 
turning OFF older libraries even though your previously existing databases 
survive on them (which is bad).  The result is that upon conversion your 
old databases fail miserably.  Whereas it's good that they're encouraging 
you to update your style of programming, it's inconceivable that you're 
going to waste valuable work time converting code in your older, already 
fine, "if it ain't broke don't fix it" databases.

To avoid this problem, open any module and click TOOLS | REFERENCES.  Make 
sure "Microsoft DAO 3.6 Object Library" is checked and high up on the 
list.  Also uncheck all those that are now labeled "MISSING" and find 
suitable replacements for them.

Also note:  The default version that Access XP saves databases is in 
Access 2000 format.  To change this, click TOOLS | OPTIONS, select 
the "Advanced" tab, and choose "Access 2002" for default file format.

Greg