Convert from V2.0 to 2K

[AlCamp]

Hello all,
I have a really basic label printing program I built in Version 2.0
some years ago.

Recently I was asked to convert application up to Access 2000.
So... I first converted it to A97, and then to A2K (I have both versions
installed)

The A2K label program is really flaky though... all sorts of weird
things happening in design mode. Somethings not right.

I think the problem may be with my old favorite... the References.

Does an app converted from V2.0 to 2K need any other references than...
VB for Apps - VBE6.dll
MSAccess 9 Object Lib - MSACC9.olb
Ole Automation - STDOLE2.tlb
MS ActiveX 2.1 - MSADO21.tlb

Thanks,
Al Camp

 

[Douglas J. Steele]

If you're converting from Access 2.0, odds are you used DAO (since ADO
didn't exist back then). That means you might also need a reference to
Microsoft DAO 3.6. If you're not using ADO, remove the reference to it.

 

[AlCamp]

Doug,
Well, I'm not sure what's going on, but this conversion is turning into a
fiasco. There is nothing at all unusual about this app... just an unbound
form where you choose some info from tables, and a report to print labels
according to the values on the form. Very vanilla code!
I have the application in A97 right now, and as far as I can see,
everything is just fine.
After I convert it from A97 to A2K nothing works reliably at all.
Totally bogus errors and weird failures too numerous to mention here.

I have other A2K apps that appear to still be running fine.

Right now, I'm going to drop back ten and punt... and try the conversion
from A97 to 2K again... and see if I can at least get a "consistent" or
"diagnosable" failure.

As always, thanks for the help.
Al Camp