Hello Ryan,

For other readers, this is in relation to the SQL Server version.

The only way that could occur is if someone with DBO privlidges made the update.  They might have, for example, obtained a "standard" chemistry lookup table from an Access version database and used that to update, or they may have edited certain values.  It might be necessary to more tightly restrict the number of DBO users.  We don't have access to your database, and it's not related to updates as there hasn't been one for quite some time, and updates don't do that action in any case.

To update chem lookup values to a previous state you could get IT to extract the values from a backup of the database.  If you have ever exported a SQL Server project to Access (File Export) that would also have exported a copy of the SQL Server Chemistry Lookup Table at the time of export. 

If you need further advice on this, just contact me off-forum, you have my details.

Regards,

Warwick

Hi Ryan,

Now you mention that possibility it is probably the most likely reason the values in the Chemistry_Lookup table were reset.  When exporting data from an ESdat Access database to the SQL database the user exports data to a "Data Interchange File", which is imported to the SQL Server database.  This can contain reference table data in addition to real site data (depends on what the user selects to transfer).  If the user indicates that the reference table data should be updated, and if that user has permissions to do so (ie DBO) then that is what will happen. 

We recommend that a few staff memebers have DBO permissions so that making required changes doesn't become a "bottleneck" however they should all be conversant with how the system works.  If necessary you can also customise the security settings so that certain people have DBO permissions, except for certain permissions and I sent information on this recently to the IT group at EBA.

Regards,

Warwick