Jump to content
Salesforce and other SMB Solutions are coming soon. ×

Using Temporary Databases


Recommended Posts

We have a FMP solution that uses more than 50 databases. So as not to exceed the limit of 50 databases, we place 44 files in a separate computer (server, host) that has FMU installed and open these 44 files to be able to be seen by other computers.

The rest (6 files) are used temporarily and resides in the users local hard drives.

The app is started on the server and works fine. But when the app started using the scripts that uses temporary tables, it cannot find these files so we have to point to the local directories. After pointing to the local directories, app also cannot find anymore the files in the server and we have to point it also to the server.

After all files have been found, things will work smoothly.

But after quitting the app and then running it again and start using the scripts, it has to locate again the files in the local and server computers.

I thought FM automatically saves the location of these files so as not to perform again these file searches.

I tried opening the files with the save relative path checked and unchecked but it still happens.


How do I store the databases local and server paths permanently so the app could always see the files?


Any help will be appreciated.

Link to comment
Share on other sites

I've never seen this happen before. It may have something to do with keeping the files on a local drive as opposed to a network drive. Have you tried storing the temp files on a network drive mounted on each computer...pointing the users FMP to the files on the network drive? Although you have to have the drive mounted at startup to have FMP see the files. Perhaps worth a try.

Link to comment
Share on other sites

The purpose that I place the temporary tables in the local hard drive because user needs first to delete all the records in these temporary tables, create new records for report and printing generation. Placing these temporary tables in the network drive and having multiple users accessing these then creating/deleting the records at the same time will probably produce disastrous results.

So my theory is to store these temporary tables in each user's local drive to avoid changes by other users of the app.

Link to comment
Share on other sites

This thread is quite old. Please start a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...

Important Information

Terms of Use