G
Guest
In a large Access 2002/VBA based application, a transfer database export
which has been working for over a year and a half suddenly does not. As of
yet I have no clue why.
The specific error message is the text of the Subject line of this posting.
Although the transfer since the beginning of its use is accomplished by a
macro, testing the same functionality within VBA and from the menu bar
(<File>, <Export>, ...) raises the same error message now.
The VBA code which emulates the macro, and also fails like the macro now, is:
DoCmd.TransferDatabase acExport, "Paradox 4.X", "somepathname", acTable,
"someAccesstable", "someParadoxtable.DB", False
The purpose is to back data from Access into a legacy Paradox application
whose usefulnes still has not been completely eliminated with Access.
To repeat, this has been a functioning macro for over a year and a half with
no issues. There has been no Access "development" on this function in that
time, especially not recently. The function is executed at the end of every
work day.
Deleting the Access table and restoring it from a backup known to have
worked does not fix the problem. Deleting the macro and doing the same
produces the same result. Placing a good backup copy of the entire database
in place of the live one and running the function produces the same error.
Double-clicking the Access table to open it and browse through it causes no
problems. Doing the same, in a sense, with the Paradox table: ditto.
Using the menu bar to export the Access table to a CSV file: no problemo,
works fine.
VBA code was used to interrogate the CurrentDB.CollatingOrder and verify it
still is '1033': general sort order.
The sense of this feels like something external to the .mdb is corrupted or
modified which controls the Access to Paradox dance. Have not yet tried
reinstalling Access, yet the problem occurs from every workstation from which
it is attempted. Have compacted and repaired early on without that resolving
the problem. Also tried creating an empty .mdb and importing all objects:
problem remained.
So what's up, amigos? Which way do I turn?
Thanks,
which has been working for over a year and a half suddenly does not. As of
yet I have no clue why.
The specific error message is the text of the Subject line of this posting.
Although the transfer since the beginning of its use is accomplished by a
macro, testing the same functionality within VBA and from the menu bar
(<File>, <Export>, ...) raises the same error message now.
The VBA code which emulates the macro, and also fails like the macro now, is:
DoCmd.TransferDatabase acExport, "Paradox 4.X", "somepathname", acTable,
"someAccesstable", "someParadoxtable.DB", False
The purpose is to back data from Access into a legacy Paradox application
whose usefulnes still has not been completely eliminated with Access.
To repeat, this has been a functioning macro for over a year and a half with
no issues. There has been no Access "development" on this function in that
time, especially not recently. The function is executed at the end of every
work day.
Deleting the Access table and restoring it from a backup known to have
worked does not fix the problem. Deleting the macro and doing the same
produces the same result. Placing a good backup copy of the entire database
in place of the live one and running the function produces the same error.
Double-clicking the Access table to open it and browse through it causes no
problems. Doing the same, in a sense, with the Paradox table: ditto.
Using the menu bar to export the Access table to a CSV file: no problemo,
works fine.
VBA code was used to interrogate the CurrentDB.CollatingOrder and verify it
still is '1033': general sort order.
The sense of this feels like something external to the .mdb is corrupted or
modified which controls the Access to Paradox dance. Have not yet tried
reinstalling Access, yet the problem occurs from every workstation from which
it is attempted. Have compacted and repaired early on without that resolving
the problem. Also tried creating an empty .mdb and importing all objects:
problem remained.
So what's up, amigos? Which way do I turn?
Thanks,