L
LarryP
I built an Access XP database on a Windows 2000 platform and it has worked
fine, but now the company is gradually transitioning to Windows XP. The
first user with Windows XP is getting an Error 2100 when a button is clicked
to open a particular form. It seems to me that the culprit is most likely
something about the different OS, but I don't know how to fix it short of
having my machine upgraded to Windows XP and rebuilding the database in that
environment. (And if I did that, I wonder if users still on Windows 2000
would then start having problems!!)
Anyone have any suggestions for a less drastic cure? So far this has only
affected one user and one database, but I have numerous other DBs out there
with many, many users, and I'd hate to think this will affect those in
similar ways when they move ?up? to XP.
fine, but now the company is gradually transitioning to Windows XP. The
first user with Windows XP is getting an Error 2100 when a button is clicked
to open a particular form. It seems to me that the culprit is most likely
something about the different OS, but I don't know how to fix it short of
having my machine upgraded to Windows XP and rebuilding the database in that
environment. (And if I did that, I wonder if users still on Windows 2000
would then start having problems!!)
Anyone have any suggestions for a less drastic cure? So far this has only
affected one user and one database, but I have numerous other DBs out there
with many, many users, and I'd hate to think this will affect those in
similar ways when they move ?up? to XP.