Reply to thread

Message

Just on another point. The refactored version was developed to enable multi-user client databases to be viable. One failing in the current refactored release is that the system doesn't know which client machine initiated a database update. To fix this, I propose to add an extra parameter in the config file called "client" where the client name can be specified (alongside "version"). I think this would be a simpler way to handle this issue than to have user logons (as MP2 allows).

I want the code to be able to feed back to each other client when data has been changed by another client. Obviously, this would require validation to be performed when MP opens to ensure that the client name is unique for the system.

If anyone has a better way of achieving this, please let me know.

I could create a separate database that stores client information. I think this approach would be more reliable than using the config files but would be slightly more work. I've used this approach for another system so could borrow that code to use here.

Any ideas welcome.

<blockquote data-quote="Anthony Vaughan" data-source="post: 1288568" data-attributes="member: 153283">Just on another point. The refactored version was developed to enable multi-user client databases to be viable. One failing in the current refactored release is that the system doesn't know which client machine initiated a database update. To fix this, I propose to add an extra parameter in the config file called &quot;client&quot; where the client name can be specified (alongside &quot;version&quot;). I think this would be a simpler way to handle this issue than to have user logons (as MP2 allows).I want the code to be able to feed back to each other client when data has been changed by another client. Obviously, this would require validation to be performed when MP opens to ensure that the client name is unique for the system.If anyone has a better way of achieving this, please let me know.I could create a separate database that stores client information. I think this approach would be more reliable than using the config files but would be slightly more work. I've used this approach for another system so could borrow that code to use here.Any ideas welcome.</blockquote>

[QUOTE="Anthony Vaughan, post: 1288568, member: 153283"] Just on another point. The refactored version was developed to enable multi-user client databases to be viable. One failing in the current refactored release is that the system doesn't know which client machine initiated a database update. To fix this, I propose to add an extra parameter in the config file called "client" where the client name can be specified (alongside "version"). I think this would be a simpler way to handle this issue than to have user logons (as MP2 allows). I want the code to be able to feed back to each other client when data has been changed by another client. Obviously, this would require validation to be performed when MP opens to ensure that the client name is unique for the system. If anyone has a better way of achieving this, please let me know. I could create a separate database that stores client information. I think this approach would be more reliable than using the config files but would be slightly more work. I've used this approach for another system so could borrow that code to use here. Any ideas welcome. [/QUOTE]