KNOWLEDGE BASE
Log In    |    Knowledge Base    |    4D Home
Tech Tip: Basic Troubleshooting Tip for 4D 2004 - Recreating "Preferences"
PRODUCT: 4D | VERSION: 2004 | PLATFORM: Mac & Win
Published On: March 19, 2008

You may find yourself in a situation where your 4D application (Single-user, Client, Server) is not behaving the way you expect it to. In some situations this can be caused by a corrupt preferences file(s). The preferences file(s) for an application typically stores the settings of any customizable features between runs, and if it becomes corrupted it can cause an application to crash or otherwise misbehave. The easiest way to diagnose preference file trouble is to move the file(s) from where the application is expecting to find it, thus causing the application to recreate a default preferences file from scratch. If this does not help you can simply move them back.

For 4D 2004 the preferences files can be found at the following locations:

Windows 2000/XP/2003:

C:\Documents and Settings\All Users\Application Data\4D
C:\Documents and Settings\_username_\Application Data\4D



Windows Vista:

C:\ProgramData\4D
C:\Users\_username_\AppData\Roaming\4D



Mac OS X:

/Users/<username>/Library/Application Support/4D
/Library/Application Support/4D



You can safely rename these directories on a PC or Mac with the exception of the "LICENSES" directory which contains the registration information for 4D 2004; if the LICENSES directory is moved you will need to re-register your 4D software. Depending on whether or not you have created any macros you may also want to preserve the MACROS folder(s).

-----
On Mac OS X there are some additional preference files that can be found in the following locations:

/Users/<username>/Library/Preferences/com.4D.*
/Users/_username_/Library/Preferences/4D*



You can safely move any of the files in those locations starting with either 4D* or com.4D.* to a different location on your machine. If this does not help you can simply move them back.
-----

Related resources:

The 4D Client structure cache

See Also: