Send Dbase To MS India Tech Support For Debugging

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Just a quick share with the group. My dbase developed in A2003 on an XP OS and saved in A2000 format works great on A2003. I get a few minor form requery errrors when running on NT with A2000 that I comment out. I had a big probelm this weekend in trying to run it on a laptop with ME OS and Access2000. I installed all the latest SP and Jet Engine Updates. Nothing but problem after problem, MS tech support in India worked with me for about 2 hours to no avail and they were great! Finally they asked me to send them the dbase to see if they can duplicate the error and find a fix. I greatly appreciate MS's willingness to do this, at no charge. However, after much frustration, I simply (%&*##^) upgraded my ME laptop to XP and installed Access 2003. Works great. Lesson learned: Access 2003-2000 dbases can't function on an ME operating system. Or can they? Just thought I would share this with all of the other developers. Thanks.
 
Windows ME is not listed as one of the supported operating systems for
Office 2003. I am surprised that Microsoft Tech Support did not tell you
that as soon as they determined your O/S. But, sometimes, software will
actually work, though it wasn't tested, on an earlier operating system and
perhaps they were as hopeful as you on that issue.

Larry Linson
Microsoft Access MVP

MBoozer said:
Just a quick share with the group. My dbase developed in A2003 on an XP OS
Click to expand...
and saved in A2000 format works great on A2003. I get a few minor form
requery errrors when running on NT with A2000 that I comment out. I had a
big probelm this weekend in trying to run it on a laptop with ME OS and
Access2000. I installed all the latest SP and Jet Engine Updates. Nothing
but problem after problem, MS tech support in India worked with me for about
2 hours to no avail and they were great! Finally they asked me to send them
the dbase to see if they can duplicate the error and find a fix. I greatly
appreciate MS's willingness to do this, at no charge. However, after much
frustration, I simply (%&*##^) upgraded my ME laptop to XP and installed
Access 2003. Works great. Lesson learned: Access 2003-2000 dbases can't
function on an ME operating system. Or can they? Just thought I would share
this with all of the other developers. Thanks.
 
I didn't know that Larry. But even though it was developedin A2003, it was saved as A2000 which does run on ME.
 
You must adjust the references in the A2K database after making changes in the A2K3 database. When running multiple versions of Access - 2K and above - always make the changes in the lowest version. The later versions handle the reference changes; however, A2K cannot handle the reference changes for the later versions and you must make them manually.
 
I have run access 97, access 2000, and access 2002 on a windows ME pc
without any problems at all.
Nothing but problem after problem,
Click to expand...

I would have checked your references...as that is the #1 problem you run
into when access works on one pc, but not on another.

For example, if your code has a reference to word, or outlook, and then you
move your code to another pc with A DIFFERENT version of word, or
outlook...then your code will break. (solution is to use late binding in
that case).

So, no, I never had any problems at all running access on a windows ME box.
And, I never had a problem moving code from my developerment pc to a pc
running window ME. It is has always worked well for me.
 
Thanks guys. I'll look at the references when I get back to the office. I've got another ME box there and see what I can do. I'm also following up with MS so I can learn more about this matter. Have a good weekend.
 
Back
Top