D
David Pate
It appears to us that the latest patch to Office XP or
Windows 2000 Professional has made the error 3001 Invalid
Argument to now appear when using the 8th parameter on the
TransferDataBase command.
DoCmd.TransferDatabase acLink, "Microsoft Access",
strDataBaseName, acTable, strTableName, strTableName, ,
True
We used the 8th parm of true to store the password to the
DB in the link connection. Then just today the user gets
the 3001 error when relinking files using the VB code.
When we remove the 7th and 8th parm from the
TransferDataBase command, the command works and the files
are linked and it appears that the password must be stored
in the link anyway without having an 8th parm of True.
Is this a bug resulting from a batch?
David Pate
University of South Carolina
[email protected]
Windows 2000 Professional has made the error 3001 Invalid
Argument to now appear when using the 8th parameter on the
TransferDataBase command.
DoCmd.TransferDatabase acLink, "Microsoft Access",
strDataBaseName, acTable, strTableName, strTableName, ,
True
We used the 8th parm of true to store the password to the
DB in the link connection. Then just today the user gets
the 3001 error when relinking files using the VB code.
When we remove the 7th and 8th parm from the
TransferDataBase command, the command works and the files
are linked and it appears that the password must be stored
in the link anyway without having an 8th parm of True.
Is this a bug resulting from a batch?
David Pate
University of South Carolina
[email protected]