Reference for Access 2000 Commands?

[Dudley]

Hi Everybody,
I'm working in the Developer version of Access XP (2002?). I keep my files in Access 2000 format. My users are often running Access 2000. Sometimes they experience run-time errors with my beast (I mean my application) because they don't have the same set of arguments for commands that I do.

For example, it looks like:

DoCmd.OpenReport "rptErrors", acViewPreview, , , acDialog

is causing somebody running "version 2000, sr-1" a problem. I'm guessing it's the number or sequence of arguments.

Is there some online reference where I can find out what proper command format is in earlier versions of Access?

Thanks!

 

[Moniker]

That's not a coding error. That's a user that hasn't downloaded all the updates/patches for their copy of Access 2000. It's telling them, "You need Version 2000, SR-1 for this to work, so go get updates." SR-1 is Service Release 1 (now called service packs).

 

[Dudley]

Hi Moniker,
I went to Office Update and see that they're up to SP3 on Office 2000, so I'll get the sr-1a person to update they're installation.

But I'm still looking for a reference site for v.2000. I'll pore through Microsoft's site, but I was hoping someone had a "better" solution.

Or, could it really be that my users are just messed up and simply need to update their installations? (I wish I could be so sure my coding was that good...)

thanks!

 

[Moniker]

I don't know where that reference is (or if it exists), but I can say I've written code that is transparent between A2K, A2K2, and A2K3 with no problem. The one issue you may have is mismatched references. For example, Access 2K uses ADO v2.6 where Access 2K3 uses ADO v2.8. Translating v2.6 to v2.8 is no issue, but if you write in Access 2K3 using v2.8 and try to get it to run on Access 2K, you'll probably get a missing reference issue. The solution, of course, is to use a reference common between all you Access version (use v2.5 for ADO, for example).

A rule of thumb, btw, is to develop in the same version or an earlier version of Access than your users so that you avoid these issues. Keeping the DB format in Access 2000 does nothing for the code base. It makes the tables, queries, etc. compatible between the two, but it doesn't guarantee code compatibility at all.

 

[Dudley]

Thanks Moniker. Is it possible to load A2k and A2K2 on the same machine?

 

[Moniker]

Look at response #3 in this post.

 

[Dudley]

Thanks Moniker. Great suggestion about different installations on different computers or hard drive partitions. I'm actually in the process of spec-ing out a new laptop, so maybe that's my answer.

p.s. I tried to "add to your reputation" but I guess I already did on another topic, and it won't let me do it again. But I sure appreciate your help today.

Sincerely,

 

[Moniker]

Hopefully you saw the link at the bottom of that. I linked the MSDN site that explains how to install multiple versions of Office on one computer.

 

[Dennisk]

I have issues with Access 2003 and Access 2000 and I suspect part of the problem is that both have the same ClassID in the registry.

So I would check to see if Access 2000 and Access XP have the same class ID if they do remove one.

I had to remove Access 2003 as it had corrupted Access 2000. However both Access 97 and Access 2000 coexist happily on my dev PC but they both have different ClassIDs in the registry.