TransferDatabase command fails

[cwald]

I have been using this command in an application for a long time all of sudden the command is not working on one of the machines using the application. This application is still in mdb format, the main reason is not all the machine is using the 2007 or greater version of Access.

Has an Microsoft update that may have gone out changed something or what could be causing the command to fail.

here is the command line i'm using: DoCmd.TransferDatabase acExport, "Microsoft Access", StrApp, acMacro, "Create New Field", "Create New Field", False

works on my machine and many others.

 

[Trevor G]

Welcome to the forum, when you say it doesn't work, what actual happens do you get a debug window stating the issue, that would help you further, also check References in the VBA screen to see if anything is shown as MISSING due to multiple versions, and finally check the Security section to see if the Macro settings are set to High as this can prevent code from running.

 

[cwald]

thanks for your response, I guess I should have been a little more clear. I have been programming in Access for many years. I have check all the items you suggested. I checked all the references and made sure the security was allowing macros. everthing is ok there.

Like I stated before, this had all worked before on this machine. And it's working great on my machine, just this one machine..

When it errors you get this option to debug or stop the macro. when selecting the debug it takes you to the VBA code and this line is highlighted.

I just don't get it!!

 

[Trevor G]

But what is the error message? Does the other machine have any addins that could be affecting this?

 

[cwald]

this is the code i'm using

DoCmd.TransferDatabase acExport, "Microsoft Access", StrApp, acMacro, "Create New Field", "Create New Field", False
DoCmd.TransferDatabase acExport, "Microsoft Access", StrApp, acModule, "Adding Field", "Adding Field", False


the StrApp = the file path of the database.

The strange thing is the second transferdatase works. so why doesn't the transfer of the macro work?


the error is "Run-time error 3994 Cannot save property; property is a schema property.

makes no sense..

the marco names are correct and everything
Now remember this did work, just started to fail.

 

[cwald]

Well this is weird, the line errors but seems to doing the transfer anyways?? This is sick..