Access over Terminal Services - Registry Format Errors

  • Thread starter Thread starter Will
  • Start date Start date
W

Will

We have just started using some Access 97 applications over Terminal
Services. On a couple of the modules (MDE's) when the startup form is
loaded, the user gets the error message:
Microsoft Access can't load the 'nu' format
The setting for this format in the Windows Registry is incorrect. You can't
save the output data to a file
in this format until you correct the setting in the Registry.
Other messages are Microsoft Access can't load the 'enu' format and
Microsoft Access can't load the 'sql_productcombo' format

On the modules where the main menu only has buttons and no fields and combos
the error messages don't appear. I have searched but come up blank, anyone
have any ideas?

Thanks
 
Always split the database into separate front-ends connected to a common
data file back-end. It is important when using Terminal Server that each
user have their own folder with their own copy of the front-end in that
folder. Never share the front-end file.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Access 97 error: "Can't load the [function-name] format." 6
access 97 1
Access 2007 Registry -> Default save format 7
Access database SQL split and Terminal Services 12
Access 2003 RT on Server 2008 R2 64bit 0
ACCESS CRASH and MDW format... 3
Access Runtime on a Windows 2008 Terminal Server 0
Error Message after exporting MS Access Table 0

Back
Top