Plug-ins need to be installed in a Win4DX (Windows standalone or client) or Mac4DX (Mac OS standalone or client) folder in the same location as your structure file. If your plug-in comes with an installer, it will almost certainly install the plug-in in some default location, in which case you will need to move the plug-in and any associated files into the appropriate 4DX folder yourself.
Plug-ins on both standalone and server versions of 4D should be installed into the same location: for a Mac OS standalone or client, Mac OS versions of any plug-ins should be installed into a Mac4DX folder in the same location as the structure file.
For a PC client or standalone, Windows versions of the plug-ins should be installed into a Win4DX folder in the same location as the structure file.
Note that this location does not depend on what type of machine the server is. Thus, in a configuration with a PC server and all Mac clients, a Mac4DX folder in the same location as the structure file is the correct location for any plug-ins.
Note also that if you have a Windows-based server with any Mac OS clients using plug- ins, the Mac OS versions of those plug-ins will need to be run through transporter before they can be used from the Windows server. This does not create a PC version of those plug-ins, but rather creates a version of the Mac plug-in that can be called from a Windows server.
It is very important if you are converting an application from v1.5/3 of 4D to 4D v6 or later that you remove any plug-ins you have installed into your structure file. All plug-ins must be installed as separate files into the Mac4DX/Win4DX folders with 4D v6 or later.
You should ideally remove the plug-in using your original installer disk. The installer should have an Uninstall option.
If this is not the case, or if you no longer have the original install disk, you can remove most plug-ins with External Mover, which came with your 4D product CD (the standard 4D installer offers External Mover as an option if you choose a custom install). Launch External Mover and open the structure file with it, then you should be able to see any externals in the structure and remove them.
If you are unable to remove an external with External Mover, it is possible to remove them by setting the resource fork of your structure to that of an empty structure file. To do this, create a new empty structure file. Then:
In 4D v6 or later, the passwords Editor allows Plug-Ins to be assigned to users in a particular access group.
You can even create a special-purpose group for access to a plug-in, and move users in and out of that group using the 4D v6/v6.5 password control commands, and thus limit use of the plug-in to a particular number of users at a time, rather than any particular group of users. In this way, you can purchase only as many plug-in licenses as are likely to be in use at one time.
4D Write v6 has a maximum length is 32,000 pixels, due to the limits of the scroll bar. 4th Dimension can only display about 40 pages of a 4D Write document on screen at any one time; the exact length depends on font, font size, and style. To use a document over 40 pages long, open it in an off-screen area, then copy and paste portions of the text to an on-screen area.
4D Write v6.5/6.7 documents have no maximum length, subject to RAM and hard disk space limitations.
4D plug-ins should be installed in a Mac4DX or Win4DX folder in the same folder as your structure file. If you are using a server with both Mac and PC clients, you will need both of these folders, and each should have a plug-in file with the same name for each plug-in you have, even if you don't intend to use a plug-in with a particular platform. You might need to create a stub file if your plug-in isn't available for the other platform.
If you are receiving a message about a plug-in being installed twice, even though you only have one copy of it in your 4DX folder, you have a copy installed in your structure or Proc.Ext file. You should remove it. (See directions above on 'How do I remove plug-ins from a 4D v3.5 or v1.5 structure?')
If you use the Mandatory Log File feature with the plug-in version of 4D
Backup, it is possible to get into a loop that will prevent you from using
your database. This situation occurs when there is no current log file for
the database. The Mandatory Log File feature will disable the database until
a new log file is created. In order to create the new log file, you must
do a full backup of the database. The problem is that you can't implement
a full backup because the Mandatory Log File feature prevents the use of
the database.
Here's how to break out of the loop. First, you must create a new data file.
This can be done either by launching the structure file and "forcing"
the Open Dialog Box to appear (by holding down the option key on the Macintosh
or the Alt key on Windows). 4D will display a dialog requesting that you
open an existing data file or create a new one. After creating a new data
file, go to the design environment and disable the Mandatory Log File feature
in the Database Properties dialog. This will allow you to open your original
data file, complete a full backup, and create a new log file.
International |
Company | Contact
4D | Site Map | Privacy
Policy | © 4D UK 1995-2008 | Change font size: [A]
[A]
[A]
| 