Distributing runtime upgrade

[donb26]

The Developer 5 manual states that if I only change the primary file of my solution and do not rename it, I don't need to rebind it. Then it says to make my changes in the original (before binding) primary file. I think I'm missing something here because the unbound file is not recognized by the runtime solution. I put the same three letter extension on it and that does not help. Plus, if the file has the same name and I instruct my end user to put it in the runtime solution folder it will replace the primary file before an import script can be run. Obviously I need help, any comments would be greatly appreciated !!

[danjacoby]

Yup, there it is, on page 4-7 of the manual.

Apparently it's wrong.

Rebind it, using the same binding key and "dot-3" extension that you originally used. Then you can replace the old primary file with the new one in the original bound solution, and it'll slip right in.

[donb26]

Thanks Dan,

There I go again, reading the directions !! When will I learn ?

Thanks for the binding advice but what about the re-naming ? Do I keep the same name or do I have to change it ?

[ March 22, 2002, 06:26 PM: Message edited by: donb26 ]

[danjacoby]

Keep the same name. Changing the name means you have to use the entire new bound solution. Not changing the name means you can slide the one file into the old solution -- just make sure you use the same binder key.

[donb26]

Thanks again.

I'm with you so far but if my updated clone(empty) has the same name when will I run my import script, won't the file with data be replaced ? Maybe I'm just a worrier !

[donb26]

Thanks for your help ! I have successfully completed my first upgrade.

[ March 27, 2002, 06:00 AM: Message edited by: donb26 ]