how do I update files in production?

[J__]

Hi,

I am going to be releasing some software to a group soon, which will run on FM7 Server Advanced. I've developed it using FM7 Developer.

I was looking ahead and thinking to myself how there are obviously going to be some updates/fixes which need to be done, once it's been rolled out to the users. But once they start entering data, then how am i to grab the database file and then make changes and put it back in without disrupting them?

Is it that you use a clone? or?

thanks for any help you can offer,

sincerely,

J__

[Reed]

It depends on the level of changes that need to be done. For quick changes, you can make them while the DB is being hosted. You can even make changes to field and account/privilege defs while people are in the DB, but it's not usually recommended.

Most people recommend that you keep a clean developer clone and never make changes to production files. You just have to make sure that when you import data from the production files that you include the set next serial value step in your import routine. Otherwise you could end up with gaps, or even worse, duplicate serial numbers.

[J__]

thanks for the response.

I was thinking along the lines of fixing a script error - not so much changing tables..

you mention a 'developer clone'. Say you have one of those, then do you import that into the production version? I know I'm wrong here.... could you elaborate a little ?

also the 'set next serial value step' .. i guess you mean if I import the data in the production db into my clone, then that becomes the new developer version right? and to make sure incrementing of auto inc fields is turned on. do i understand that correctly?

thanks,

J__

[Reed]

When you are done working on you DB, you choose save a copy as... then choose clone (no records) from the popup. Then you can export all the data from the production file, and import it into the clone. Or, you could import the data directly from the production files into the clone. Then just close the production file using the server admin tool, and replace the production file with your new file.

When you import the data into the clone, records will keep the serial numbers they have, but in the field definitions, the next serial value will likely be set to some number other than the number following the newest record. So you have to set that either by manually going into the field definitions or by using the script step that can do the same thing.

[J__]

Hi Reed,

I know it's been a while, but hey, timelines happen and so do deadlines...

I'd like to follow up here with a few questions.

I don't completely follow the second section. Are you saying that after I import the data from Production into my clone the serial numbers will not match? So, basically your saying that the Clone I have will have had the serial set to say 10 and during that time, the production versions serial has been incremented, so the next serial wouldn't match. Is that right?

So, does this mean that if I was to import the data and then do a test, like add a new contact, that the serial for the contact could be 11 rather than the last number of the production contact's serial+1 ?

Or does the serial memory get carried over?

Also, to import say 5 tables, Don't i need to then pick import for each table and match the fields?

i think i can do this in a script step right?

i look forward to feedback on my questions and any other tips /hints/guidelines in this area.

thanks so much,

Sincerely,

J__