Multi-user Issues

Top  Previous  Next
Added alphabetical sorting of the list of providers in the selection window.
Made the trial and satellite versions essentially the same. Once there are more than 25 accounts, the data is rendered read-only. Satellite clients no longer require a registration number, they can just use the trial version. Also adjusted some additional functions to ensure no errors occurred when the satellite file was made read-only.
Maintenance log adjusted for multiple provider versions to record all entries for last 13 months (single user versions continue to record last 5000 entries even if longer than 13 months).

 

Bugs fixed

 

Adjusted the provider selection function to ensure that if a data file is not attached or refreshed correctly, a definitive reattachment method is done automatically. This is to avoid having a data file reattached but the forms not refreshed (& vice versa) to avoid confusion in the data.
Fixed bug where splitting a single user file into a mult-user file did not correctly delete site tables from user file. This could cause another bug where registering multi-user version may set user file to be the site file.
Since the EmptyMU.aau file was abandoned, multi-user data files have been created without default values. This was a problem for some fields, and was fixed as follows. Default PaymentsT!PaymentType and PatientsT!CreationDate are now inserted by the form control. PaymentsDeletedT!DateDeleted and PaymentsDeletedT!ReferredAccounts are inserted in a code procedure. Checked that all other fields did not need a default value in the table. Set some other defaults in the PatientsF form.
The data file creation function sets AllowZeroLengthFields to True for all text fields in hic_* tables.
Data file creation function creates primary and other indexes on relevant tables in 3 hic_* tables.
Put DBEngine.Idle dbRefreshCache into data file opening procedure (2) to improve networking issues.