Conversion Advice

L

LisaInAz

I have read posts on conversion and was wondering if someone could take a
guess as to why I had issues or if I should try to convert again. I think
this is the right place for this question

I have ACCESS 2002 on my workstation, inherited a dBase written in ACCESS
2000, Customer has ACCESS 2003 on workstation. We all have XP OS.

When I attempted to convert from 2000 to 2002, I thought all was well until
I passed it to the customer, the back end sits on the server the front end is
dragged to desk top

I used the ACCESS 2002 dBase Converter and I also used the dBase Splitter.
From posts here I, set autocorrect off, compact on exit off, record locking
is on (i have multiple user editing), and it is "shared"

Both my customer and I had a problem using the fe after the first time it
opened. Any consecutive time to open we received "Microsoft Access has
detected a corruption of file error". I initally thought it had to do with
Exiting Access using the Red X in the right corner. According to a post that
shouldn't matter. I also had the customer exit out using the "button" on the
switch board for exit. Still had issues.

Compacted and repaired the backend and I attempted to Compact and repair
(from the posts here), used Jetcomp.exe, I tried to create another dBase and
import all my objects 1 at a time, with no success to the front end. Also
tried Convert from 2002 back to 2000.

From different Posts from here and reading allenbrowne web site I
accomplished the following:
I ended up creating a separate backend and separate front end in ACCESS
2000, Imported all my tables to the backend and imported all my objects to
the front end.
In the fe I recompiled the code, in references have checked VB for
Applications, Microsoft Access 10.0 Object Library, Microsoft DAO 3.6 Object
Library and OLE Automation (not sure if I need this or not), set autocorrect
off, compact on exit off, record locking is on (i have multiple user
editing), and it is "shared".

Now the front end seems to be working (I have not created and MDE) fine.

I was wondering if any one experienced a simliar issue
What advice could one give to upgrade Convert Access 2000
Even though it now works does anyone think I missed something going back to
Access 2000.

I appreciate anyones best guess and any suggestions.
Thanks
Lisa
 
A

Arvin Meyer [MVP]

You can use the Access 2000 version mdb file format on every version
subsequent to that. I typically use that format to avoid any conversion
issues, and it's worked fine. Obviously proprietary new format features
cannot be used.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top