C
clh333
I am a developer working on an established application, for which I am
writing code behind a form inteded to convert, update and extend users' data
files from Access 97 to Access 2000 file format. (The new app runtime will
be Access 2003).
After designing I began testing against user data files which had been
submitted in the past to Support for assistance with problems. Here I
discovered the problem that prompts me to write today:
One user database file has a corrupted table which generates an error when
my VBA code tries to extract the Access 97 data, using a qdf, and inserti it
into its 2000 counterpart. Using Access 97 from the UI we can successfully
repair and compact the data, and import it thereafter. However, from within
my Access 2003 form's code module, I am unable to achieve the same result.
I have tried the two methods I could find in the help files. Both ran
without error, creating the compacted, renamed version. Neither removed the
source of the problem, however, and so the procedure fails on subsequent
execution of the qdf.
We would prefer not to ask the users to perform a compact-and-repair before
initiating the update, but I don't know of a way around this step.
Can anyone suggest another approach?
Thank you for your assistance.
CLH
writing code behind a form inteded to convert, update and extend users' data
files from Access 97 to Access 2000 file format. (The new app runtime will
be Access 2003).
After designing I began testing against user data files which had been
submitted in the past to Support for assistance with problems. Here I
discovered the problem that prompts me to write today:
One user database file has a corrupted table which generates an error when
my VBA code tries to extract the Access 97 data, using a qdf, and inserti it
into its 2000 counterpart. Using Access 97 from the UI we can successfully
repair and compact the data, and import it thereafter. However, from within
my Access 2003 form's code module, I am unable to achieve the same result.
I have tried the two methods I could find in the help files. Both ran
without error, creating the compacted, renamed version. Neither removed the
source of the problem, however, and so the procedure fails on subsequent
execution of the qdf.
We would prefer not to ask the users to perform a compact-and-repair before
initiating the update, but I don't know of a way around this step.
Can anyone suggest another approach?
Thank you for your assistance.
CLH