Is there a resource where I can learn about each of the file types that make up an Alpha5 application?
Situation: We have installed a runtime system on a client's network. The client has entered some data into the system and continues to enter data.
A couple of weeks back, we took the master copy of the database application and began to make some changes. We added a field to 5 .dbf tables and added another Child Member to a Set. We redesigned a couple of forms and testing the system and like what we have.
Now it is time to update the client's system. Obviously, we cannot just replace all the old files with the new ones: we would lose and data entered between the time we took a copy for our development and testing purpose and the time we install the changes.
I believe that what I need to do is to copy all the changed files, save the .dbf files to the system on the Server. Then, go into the Server's runtime and make the changes to the database tables. The change is simple: it is just adding an automatic date stamp to any new records created going forward. The SET changes are just adding a new Child link.
Am I correct in assuming that none of the other files will affect the actual data on the networked application?
Of course, when we are done, we will need to make and distribute new shadow files that match the new database structure.
Situation: We have installed a runtime system on a client's network. The client has entered some data into the system and continues to enter data.
A couple of weeks back, we took the master copy of the database application and began to make some changes. We added a field to 5 .dbf tables and added another Child Member to a Set. We redesigned a couple of forms and testing the system and like what we have.
Now it is time to update the client's system. Obviously, we cannot just replace all the old files with the new ones: we would lose and data entered between the time we took a copy for our development and testing purpose and the time we install the changes.
I believe that what I need to do is to copy all the changed files, save the .dbf files to the system on the Server. Then, go into the Server's runtime and make the changes to the database tables. The change is simple: it is just adding an automatic date stamp to any new records created going forward. The SET changes are just adding a new Child link.
Am I correct in assuming that none of the other files will affect the actual data on the networked application?
Of course, when we are done, we will need to make and distribute new shadow files that match the new database structure.
Comment