03-12-2010 02:21 AM
When creating a new Integrity Checker test to update a table it seems to automatically update the MODIFYDATE of that table, even though it is not in the UPDATE statement for the test. Is there any way of stopping that from happening. We have sometimes to fix the data in one field in all records in the table due to a bug but don't want to change the modifydate as there is some other functionality that relies on this date to include/exclude records in an automated export - this should be based on user modification.
03-12-2010 05:08 AM
It's the SalesLogix provider that is doing it automatically. IF an Update or Insert (be it SQL statements or an ADO recordset) does to specify a value for:
A - CREATEDATE
B - CREATEUSER
C - MODIFYDATE
D - MODIFYUSER
Then the provider will do it automatically.
03-12-2010 05:46 AM
03-12-2010 07:13 AM
Not disagreeing.. however, it took years (.. and years) to get all the table in SLX to have the 4 basic fields. For the longest time, SalesLogix felt that we did not need them on all the tables (ex: "internal tables w/metadata"). They finally saw the light. Having the provider do certain functions for us was also a great stride forward.
As far as anything changing (now).. I'd bet 100% no.
03-12-2010 07:35 PM
03-12-2010 10:01 PM