February 1, 200619 yr The key is of your own creation. It shouldn't be easily 'guessable'...a mix of text and numbers is best. You'll need to use the same key when creating updates to the solution. Steve
February 1, 200619 yr Author Thanks Steve Think ive phrased things badly. will try to be more precise. I have a seperate file for data and one for gui, if i create a rungtime using both files they are merge into one .usr file. If i then want to update the gui i presume this will overwrite the data as well. Is there a way to set up two run times independent of each other but wherby the gui runtime can access info from the data runtime? Then when i need to update the gui it wont overwrite the data as well. Understand this can be done via scripted import/export but wanted to avoid that route if possible.
February 1, 200619 yr if i create a rungtime using both files they are merge into one .usr file I don't think so.
February 2, 200619 yr To start with, you're best off not using a '.usr' extension...if you are, I'd suggest changing to something that doesn't exist. There is a site that lists all in use extensions. I would bind both files together using the same binding key. Then, if you have to replace the GUI, just replace it. While I'm not certain, I think FM would barf with what essentially would be 2 runtimes. Steve
March 18, 200619 yr I have gotten in the habit of building in a password locked export routine for the data in any runtimes I distribute. That way we can get the data out regardless of major upgrades. I've also built one that allows for multiple users to sync data with export /import to mimic a larger solution. Works pretty good.
July 23, 200619 yr I would greatly appreciate any "best practices" that you've developed to upgrade runtimes. I'm wrapping up dev of version 1 and want to include "hooks" for a smooth upgrade process. All advice welcome.
Create an account or sign in to comment