M
Max Moor
Hi All,
I have a 2002 app that's been out for some time. In the past, I've
only ever updated the front end, so it's been easy to release patches. Now I
want to release a patch that adds a couple of fields to a backend table and
changes some properties of existing fields. I'm wondering how folks "in the
know" handle this?
I don't want to replace the backend and try to move the data from the
old one to the new one. It seems more straight forward if I run backend
update code from the new front end. The code in the front end can tell if
the update has been done. If it hasn't, it will do the updates as needed.
Maybe I could keep a flag in the front end tracking if the uupdates have been
done, so I don't have to run the test code with every start of the app?
Does this sound sensical and doable? Is there a better way to do
backend updates? I appreciate any advice on the matter.
Regards,
Max
I have a 2002 app that's been out for some time. In the past, I've
only ever updated the front end, so it's been easy to release patches. Now I
want to release a patch that adds a couple of fields to a backend table and
changes some properties of existing fields. I'm wondering how folks "in the
know" handle this?
I don't want to replace the backend and try to move the data from the
old one to the new one. It seems more straight forward if I run backend
update code from the new front end. The code in the front end can tell if
the update has been done. If it hasn't, it will do the updates as needed.
Maybe I could keep a flag in the front end tracking if the uupdates have been
done, so I don't have to run the test code with every start of the app?
Does this sound sensical and doable? Is there a better way to do
backend updates? I appreciate any advice on the matter.
Regards,
Max