[AccessD] A2K Corrupts Database Created in AXP - A2K Format

That turns out to be EXACTLY the problem!  The work-around suggested by 
the knowledge base article is amazing - essentially copy all module code 
into text files appropriately named, of course, then tell iAcces that 
they don't have modules behind them.  Make a blank database and import 
all the database objects - then, one at a tiime, copy the text files 
into modules for all the objects.  I found a simpler way while we wait 
for the IT people to download and apply the appropriate service pack 
(SR1 is already there).  The real issue turned out not to be copying the 
database from my machine to the problem machine; it turned out to be 
importing new or revised objects from a "patch" database - that is, one 
that just contained updated information or new forms or reports - using 
A2K for the import.  My temporary solution was to bring the bad database 
back over to my machine, create a new blank database, and import into it 
the appropriate objects from the toasted database and from the updating 
"patch" database - check that the database functioned correctly on my 
machine, then copy back to the problem machine.  Worked perfectly.  This 
coming week the IT people should have the Office 2K SP-3 installed and 
we can quit playing this game.  Thanks for the help.  I really learned 
something to watch out for here - always useful.
Tina

Charlotte Foust wrote:

>Does the A2k machine have the service packs installed?  Vanilla A2k had
>a problem with the version of the VBE6.dll installed by the XP version,
>which caused the project to get thoroughly toasted in 2000 if the
>patches weren't in place.  Could this be your situation?
>
>Charlotte Foust
>
>
>-----Original Message-----
>From: Tina Norris Fields [mailto:tinanfields at torchlake.com] 
>Sent: Monday, January 03, 2005 11:06 AM
>To: accessd at databaseadvisors.com
>Subject: [AccessD] A2K Corrupts Database Created in AXP - A2K Format
>
>
>Okay, help!
>
>I made a little database with some nice parameter queries and selection 
>combo-boxes.  It looks great and works perfectly here on my computer - 
>WinXP, AXP using A2K file format.  When I copy it onto the machine where
>
>it will be used, it doesn't work  It is to be used on a Win98 machine 
>using A2K.  If I create a blank database and import all the tables, 
>forms, queries, reports, and modules, it works perfectly - until I close
>
>the database and reopen it.  At that point, the silly thing behaves as 
>though corrupted.  Trying to open a form from within the database window
>
>gets the message that the file can't be found!  What little nasties do I
>
>need to know about how to make AXP and A2K play nicely together?
>
>I know it will be something that everybody else is aware of and I'm not!
>
> TIA
>
>Tina
>
>  
>