VB Using A2000 MDB

[Tim Marshall]

I have a user who has what I assume is a VB application: it's opened
with an exe file, there are numerous dll files in the directory in which
the executeable resides, along with an mdb file that I could not open in
A97, but can open in A2003.

Assuming I'm probably correct that this is a VB application, what part
of A2000 (the vintage of the application is such that it was installed
before A2002) is actually installed, or does it need to be installed at
all with the VB program?

Several years ago, after this program was installed, his A97 references
started to go wonky, similar to behaviour I saw in installations with
A97 and inmproperly installed A2K.

Thanks in advance for any comments.
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me

[MGFoster]

Tim Marshall wrote:

I have a user who has what I assume is a VB application: it's opened
with an exe file, there are numerous dll files in the directory in which
the executeable resides, along with an mdb file that I could not open in
A97, but can open in A2003.

Assuming I'm probably correct that this is a VB application, what part
of A2000 (the vintage of the application is such that it was installed
before A2002) is actually installed, or does it need to be installed at
all with the VB program?

Several years ago, after this program was installed, his A97 references
started to go wonky, similar to behaviour I saw in installations with
A97 and inmproperly installed A2K.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Probably, just the JET DLL was installed to control the .mdb file.

You're probably correct about the improper installation of A2K. I
believe the fix was to uninstall A2K, change a font file name (which
name escapes me), and reinstall A2K. Don't know how you'd do it for
just a JET DLL.

--
MGFoster:::mgf0 0 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQi32sIechKq OuFEgEQLyIQCg90 Ug8O5v8sDPiTarn 4vMEaeErrIAn2Qy
I3gDJvkfHKnqxtX upwoDq3/g
=COry
-----END PGP SIGNATURE-----

[Larry Linson]

"MGFoster" wrote

You're probably correct about the
improper installation of A2K. I
believe the fix was to uninstall A2K,
change a font file name (which
name escapes me), and reinstall A2K.
Don't know how you'd do it for
just a JET DLL.

Mike, the fix you describe is for avoiding the "No License" message when you
try to install Access 97 -- the font is HATTEN.TTF, but it won't help in
this case, AFAIK.

Classic VB (through VB6) would have installed Jet. Jet 4.0 (the one used
with Access 2000 and later) has had several (8, I think) Service Packs,
which should be applied.

A possibly pertinent Knowledge Base article is 238401. Visit
http://support.microsoft.com and take a look at it. VB6 originally came with
Jet 3.5x (the one used with Access 97) and this deals with using VB6 with
the more-recent Jet 4.0.

Larry Linson
Microsoft Access MVP

[Tim Marshall]

Larry Linson wrote:

A possibly pertinent Knowledge Base article is 238401. Visit
http://support.microsoft.com and take a look at it. VB6 originally came with
Jet 3.5x (the one used with Access 97) and this deals with using VB6 with
the more-recent Jet 4.0.

Thanks Larry, I'll check this one out.

--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me