stefanshotton Posted February 1, 2006 Posted February 1, 2006 Using fmpro 8 advanced, not used binding before.how do you set up the key?
SteveB Posted February 1, 2006 Posted February 1, 2006 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
stefanshotton Posted February 1, 2006 Author Posted February 1, 2006 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.
comment Posted February 1, 2006 Posted February 1, 2006 if i create a rungtime using both files they are merge into one .usr file I don't think so.
SteveB Posted February 2, 2006 Posted February 2, 2006 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
CoZiMan Posted March 18, 2006 Posted March 18, 2006 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.
bcooney Posted July 23, 2006 Posted July 23, 2006 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.
Recommended Posts
This topic is 6696 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now