[AccessD] A2K MDE on A2002

Rocky,

I think that this is exactly what is going on.  I use a lib as you know.  At
one client I have a mix of systems running A2K, AXP and A2003.  I develop in
A2K.  The non A2K systems REQUIRE a recompile of the lib AND the MDB that
uses the lib before they will run.  I get a page fault otherwise.

I do know that AXP and above install a new version of VB6.  It appears that
this new DLL "breaks" the A2K apps.  Recompiling with AXP uses that VB6 DLL
and "fixes" whatever the problem is.

John W. Colby
www.ColbyConsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Rocky Smolin -
Beach Access Software
Sent: Saturday, April 24, 2004 1:59 AM
To: AccessD at databaseadvisors.com
Subject: [AccessD] A2K MDE on A2002


Dear List:

I had a client call this morning installing a system at a customer site. He
took the mdb which was created in A2000, made an mde in A2000, then put that
mde on the customer's machine which was running A2002.  It failed on opening
the first form with an error that indicated either a compile error or a
missing reference.

So I had him put the A2000 mdb on the A2002 machine.  Compiled fine.  No
missing references.  But the 'Make an MDE' button was grayed out.  So I had
him convert this A2000 MDB to A2003.  Then he could make an MDE and it ran
just fine.

So is it the case that an A2000 MDE will not run on A2002 (or A2003)?

MTIA

Rocky Smolin
Beach Access Software
http://www.e-z-mrp.com

--
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com