I have read the help files and many forum messages on this subject and I am still confused. Perhaps I am dense and missed it.
I do not know how the "version number" works with Network Optimization. It seems a simple explanation of what is happening could be added to the help file. But maybe it's not so simple, given that I have spent hours reading and still don't know what the *ell is going on.
Here's my question, as simple as I can ask it:
How do I make sure that the shadow databases (on the workstations) are updated to the latest version of the master database (on the server) when I decide to make a change to said master database?
I know it has something to do with using a "version number" but I don''t know where to put this version number in the master database. When using a shadow copy (user is sitting in front of a workstation and using the Run Engine version of A5), where does A5 look in the master database for this version number. How do I get the version number I want into the proper location so that the shadow copy will find it?
I usually make changes directly on the server using my developer's version of the A5 program. When I make a change to a form on the master database (on the server) I want to make sure that same change is going to show up on the shadow copies of the database (on the workstations).
I have never used Network Optimization before. Instead, I had the workstations sharing the master database. The changes I made were automatic and instant (once the application was closed and then opened again). I'm still confused as to how I can achieve the same results when using Network Optimization.
Can anyone explain what is happening behind the scenes when using A5 Network Optimization? What is happening on the workstations? What is happening on the server? Is the version number only set at the server copy? If so , how? If not, what else is needed by the shadow copy to get the message to update?
Thank you,
Sean
I do not know how the "version number" works with Network Optimization. It seems a simple explanation of what is happening could be added to the help file. But maybe it's not so simple, given that I have spent hours reading and still don't know what the *ell is going on.
Here's my question, as simple as I can ask it:
How do I make sure that the shadow databases (on the workstations) are updated to the latest version of the master database (on the server) when I decide to make a change to said master database?
I know it has something to do with using a "version number" but I don''t know where to put this version number in the master database. When using a shadow copy (user is sitting in front of a workstation and using the Run Engine version of A5), where does A5 look in the master database for this version number. How do I get the version number I want into the proper location so that the shadow copy will find it?
I usually make changes directly on the server using my developer's version of the A5 program. When I make a change to a form on the master database (on the server) I want to make sure that same change is going to show up on the shadow copies of the database (on the workstations).
I have never used Network Optimization before. Instead, I had the workstations sharing the master database. The changes I made were automatic and instant (once the application was closed and then opened again). I'm still confused as to how I can achieve the same results when using Network Optimization.
Can anyone explain what is happening behind the scenes when using A5 Network Optimization? What is happening on the workstations? What is happening on the server? Is the version number only set at the server copy? If so , how? If not, what else is needed by the shadow copy to get the message to update?
Thank you,
Sean
Comment