ACCESS 2007 Runtime Warning Windows Issue

I have a data form developed in ACCESS 2007 and I have set it up for the runtime mode.  It works perfectly on the machine I created it on, but I get warning windows when it is first opened and I get ten warning windows in a row when I send 10 table to an external database.  I get the errors with DoCmd.TransferDatabase  but I don't get the errors when I export an Excel spreadsheet with DoCmd.TransferSpreadsheet.  The code below is what gives the error, but for documentation, here is the code that created the file to receive the exported tables.

Private Sub cmdExportMDB_Click()
'This refresh is necessary since the refresh rate is the frequency of saving changes back to the table.
'The default refresh rate can be set by the user but the default value is 60 seconds so if the data are
'copies to a file less than 60 seconds after a change, the change does not occur in the output file.
Dim db As DAO.Database
'create a string variable to use as a test for the presence of the WF87Link.mdb file
Dim TestLinkFile As String
'If the file exists, DIR will return the file name, if not it will be a blank string
TestLinkFile = Dir("C:\WetForm\WF87Link.mdb")
'This tests for the existence of the file, if the file doesn't exist then it is created.
If TestLinkFile = "" Then
Set db = CreateDatabase("C:\WetForm\WF87Link.mdb", dbLangGeneral, dbVersion40)
Set db = Nothing
End If
DoCmd.SetWarnings False
DoCmd.TransferDatabase acExport, "Microsoft Access", "C:\WetForm\WF87Link.mdb", acTable, "WetForm", "WetForm", False
DoCmd.TransferDatabase acExport, "Microsoft Access", "C:\WetForm\WF87Link.mdb", acTable, "WetForm2", "WetForm2", False
DoCmd.TransferDatabase acExport, "Microsoft Access", "C:\WetForm\WF87Link.mdb", acTable, "SpeciesLookup", "SpeciesLookup", False
DoCmd.TransferDatabase acExport, "Microsoft Access", "C:\WetForm\WF87Link.mdb", acTable, "SoilInfo", "SoilInfo", False
DoCmd.TransferDatabase acExport, "Microsoft Access", "C:\WetForm\WF87Link.mdb", acTable, "State_County", "State_County", False
DoCmd.TransferDatabase acExport, "Microsoft Access", "C:\WetForm\WF87Link.mdb", acTable, "VegRemark", "VegRemark", False
DoCmd.TransferDatabase acExport, "Microsoft Access", "C:\WetForm\WF87Link.mdb", acTable, "SoilRemark", "SoilRemark", False
DoCmd.TransferDatabase acExport, "Microsoft Access", "C:\WetForm\WF87Link.mdb", acTable, "SprintDB_SysTable", "SprintDB_SysTable", False
DoCmd.TransferDatabase acExport, "Microsoft Access", "C:\WetForm\WF87Link.mdb", acTable, "PhotoLocations", "PhotoLocations", False
DoCmd.TransferDatabase acExport, "Microsoft Access", "C:\WetForm\WF87Link.mdb", acTable, "HydRemark", "HydRemark", False
DoCmd.SetWarnings True

Open in new window

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
What are the "warning windows"? Can you post the exact message you receive?

What OS are you running this on?

phmurphyAuthor Commented:
It had a lot of text and a screen shot of it is attached.
Security Notice
A Potential security concern has been identified.
Warning: It is not possible to determine that this contend came from a trustworth source......

File Path: C:\.....
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
The .Doc file won't open. Please post an Image file (.jpg or .png) instead - I really, really don't like opening .doc files, had too many bad experiences with them.

You can get a free screenshot capture tool here:

Again: What operating system are you running this on? Vista, XP, etc?

The database you're trying to export to - is this in a Trusted Location? This can be checked in the Access Options section ... if it's NOT in a Trusted Location then I'm not sure how you can get those warnings to go away.
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

phmurphyAuthor Commented:
Thank you for your response,
The .jpg is attached. - I get this same type of error when the runtime opens.
I have Windows XP Pro Sp2 on my main machine,, the others have the same.

The folder where the .mdb is coming from and the folder where the files/tables are being copied to are in trusted locations.  Does the trusted location travel with the runtime?  In other words, if C:\WetForm and its subfolders is trusted on the main machine, is the same path trusted on the others?  Since the other machines don't have ACCESS 2007 loaded on them, there is no way to set the trusted locations on the other machines.  They do happen to have ACCESS 2003 loaded on them, but there is no "Trusted Zone" settings in 2003 as far as I know.
phmurphyAuthor Commented:
Also, no errors occur when I run the same file as an .mdb in ACCESS 2003 on the other machines.
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
How about this:


I found this on Google

Try this:

In Registry Editor, locate the following registry subkey:

1) Click the registry subkey, point to New on the Edit menu, and then click Key.
2) Type Security, and then press ENTER to name the key.
3) On the Edit menu, point to New, and then click DWORD Value.
4) Type DisableHyperlinkWarning, and then press ENTER to name the entry.
5) In the right pane, right-click DisableHyperlinkWarning, and then click Modify.
6) In the Edit DWORD Value dialog box, click Decimal, and then type 1 under Value data.

Note A value of 0 enables the hyperlink warning message. A value of 1 disables the hyperlink warning message.
7) Click OK.
8) Exit Registry Editor.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
phmurphyAuthor Commented:
I need to have something that doesn't require the client to go to the registry.  However the link to the microsoft site identifies the bug and provides some work arounds.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.