While in Access Runtime OutputTo Fails

I don't know if this is the problem in your specific case, but here is the cause of the problem and the solution as posted in the public forums:

the runtime is looking for Utility.accda which is in the \Accwiz folder and which the runtime doesn't know about. Copying the file UTILITY.ACCDA from the ACCWIZ directory to the same directory as MSACCESS.EXE fixes the problem.

HTH

I tried this on two PCs, but still a no go. It just showed up on another PC in a different program that's been running for years. Think there was some sort of patch that Microsoft did that starting to cause this error? Very frustrating.

 

If you are converting to Access 2007 RunTime, the following link will download sp1 which contains a fix for errors related to the OutputTo in Access 2007 Runtime.

              http://support.microsoft.com/kb/943249
If you are still using Access 2000 Runtime, and have not converted to Access 2007 RunTime, the only other thing I can think of is to make sure you don't have any missing vb library references, particularly to the DAO3.6 dll

Actually, I am testing this with two runtime versions. One is created using the MSAccess tools, the other is created using the WiseINstalltion using the SageKey scripts. They both are bvased off Access 2000 runtime files.

DAO360.dll reference? Well, what's odd is that these applications have been running years without a problem, so they must have their refernces set correctly. The other issue may be that another program that has been installed (which is done regularly) may have placed a second DAO360.dll in some other folder and then registered it. Is it possible the app is confused on which DAO360.dll to use? For instance, I found a few on a PC in places like C:\windows\system32  or maybe the  "C:\Program Files\Common Files\Microsoft Shared\DAO. Think this could be the problem?

Not confused as to which one, but where to find it if it is in a different location then the location it was in when the reference was set, or missing altogether.

"it if it is in a different location then the location it was in when the reference"

That's possible but remember, this is not an issue with the full version of Access, only runtime. You would think, if that was the issue, it would affect both.

Is there a way to find in the registry which one(s) have been registered and where they are. I did a search and had some hits on DAO360.dll, but cuoldn't figure out which was registered and which wasn't.

See this link:
http://support.microsoft.com/kb/209849/

Actually, I was looking for a way to look in the registry itself to find which DAO360.dll has been registered in Windows and where it was located.

I never monkey with the registry...too risky....the code I gave you should tll you what you need to know...

Here is something else you can try.....place a copy of DAO3.6 and any actively used OCX files in the same directory/folder as the database file. i understand that when access can't find a referenced file in its normal location, it checks for it tn the db folder before raising an error.

"the code I gave you should tll you what you need to know..."

I don't quite agree. The code won't tell me whether the dll is registered or not within the Windows Environment, it just tells me that Access as referenced the file. I can unregister all those files and Access will still show them in the list. Wether or not the file is actually registered in the 'Windows Registry' is different then viewing it in the References dialog in Access. I'd like to find out if the file is actually regfistered when the Regsvr32 is executed. And if sucessful, where in the registruy that info is stored. I have no plans to change the registery, just get some info from it.


I'll try you other idea now.

in re: registry, I don't know because I never monkey with it.

If you still having problems, try the OutputTo using the snapshot format.

Unfortunately, I can't because they may need to fine tune the doc before the end up emailing it out. RTF is the only option

see these links about references(very interesting) :

http://www.wiredbox.net/Forum/Thread11708_Access_2003-Broken_reference-not_finding_library_in_subdirectory.aspx

http://www.tek-tips.com/viewthread.cfm?qid=1508141&page=1