G
Guest
I'm trying to use the docmd.transferdatabase method. I have a test database
(OriginalTemp.mdb) on one drive (E with a table called 'Customer' in it.
On my C: drive I have a similar database called Temp.mdb. My latest attempt
at coding looks like this:
DoCmd.TransferDatabase acExport, "Microsoft Access", _
"E:\OriginalTemp.mdb", acTable, "Customer", _
"C:\Temp.mdb", , False
When I try to run this (through 'click' on a form button) I get the
following message:
"The Microsoft Jet database engine could not find the object 'Customer'.
Make sure the object exists and that you spell its name and the path name
correctly." I, obviously, am doing something wrong. I have been able to get
this to work with acLink when using the same drive letter, in another
experiment. I also don't understand how the method tells 'where' to transfer
the Customer table to (in reviewing the newsgroup, I note that someone had
used the new table name where I put in the 'C:\Temp.mdb'...but that didn't
seem to work either. I've checked and re-checked for a typo, but don't see
one.
Any suggestions? Scott
(OriginalTemp.mdb) on one drive (E with a table called 'Customer' in it.
On my C: drive I have a similar database called Temp.mdb. My latest attempt
at coding looks like this:
DoCmd.TransferDatabase acExport, "Microsoft Access", _
"E:\OriginalTemp.mdb", acTable, "Customer", _
"C:\Temp.mdb", , False
When I try to run this (through 'click' on a form button) I get the
following message:
"The Microsoft Jet database engine could not find the object 'Customer'.
Make sure the object exists and that you spell its name and the path name
correctly." I, obviously, am doing something wrong. I have been able to get
this to work with acLink when using the same drive letter, in another
experiment. I also don't understand how the method tells 'where' to transfer
the Customer table to (in reviewing the newsgroup, I note that someone had
used the new table name where I put in the 'C:\Temp.mdb'...but that didn't
seem to work either. I've checked and re-checked for a typo, but don't see
one.
Any suggestions? Scott