By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,077 Members | 2,160 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,077 IT Pros & Developers. It's quick & easy.

Conversion: Access 2000 to Access 2003

P: n/a
Deb
All 12 of my department's machines are being converted next week from
Windows 2000/Office 2000 to Windows XP/Office 2003. I have downloaded
the Migration document from Microsoft for distribution but would like
your input regarding Access as many of our group use it.

I am concerned especially about linking to other Access databases. And
about connecting to Dbo data. We also regularly connect to and from
Excel files.

All of our databases are rather small, and we do not share many, so SQL
Server is not an issue.

Looking forward to hearing your insight.

Dec 8 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
As Lyle and David can attest to, I've had a bad deal with Office 2003
on Windows XP. For whatever reason, Access 2003 imported about 5 times
as many records as it was supposed to when working with ONE query only.
No other queries displayed this problem. It seems to have something to
do with Access' interaction with dBASE IV files. I don't know if this
problem exists when using other types of external files.

In a nutshell, it seems to me that you will probably have a number of
problems at first, but you will eventually find them all and either be
able to fix them or create workarounds for them.

Dec 8 '05 #2

P: n/a
"Deb" <ko*****@swbell.net> wrote in
news:11**********************@g43g2000cwa.googlegr oups.com:
All 12 of my department's machines are being converted next week
from Windows 2000/Office 2000 to Windows XP/Office 2003. I have
downloaded the Migration document from Microsoft for distribution
but would like your input regarding Access as many of our group
use it.

I am concerned especially about linking to other Access databases.
And about connecting to Dbo data. We also regularly connect to
and from Excel files.

All of our databases are rather small, and we do not share many,
so SQL Server is not an issue.

Looking forward to hearing your insight.


I've never had a single A2K application that didn't run problem-free
in A2K3, without any conversion or any adjustements to code or
anything else.

I don't know what you mean by "Dbo" data, though.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Dec 8 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.