How can I get column-level conflict checking in a replica set converted from Jet 3.x to Jet 4.0?
When you convert from a Jet version before 4, the older default bahavior (row-level conflict tracking) is retained, so the ColumnLevelTracking property is set to FALSE. You cannot change this property in a replicated table. The only way to change the ColumnLevelTracking property is to unreplicate the table, uncheck the Row-Level Tracking checkbox in the table properties, then re-replicate it. This, of course, has to be done in the Design Master. Also, you can’t unreplicate a table that participates in relationships, so you’ll need to remove relationships, unreplicate, uncheck row-level tracking, and then re-replicate, and restore the relationships. The quick checklist: • using the database documenter, print out your existing relationships (for reference in making sure you restore all of them correctly after this process). This is found on the Tools menu under Analyze. • remove relationships to the first table you’re going to change. • open the table properties sheet (the one you get by
Related Questions
- Hi Dave, That would be the first thing I would do after checking the coolant level is replace the thermostat as it could be stuck open. Heater cores get plugged and programmers fail to go to the full heat position also. Put in the new stat and your problems might be over.
- Does Minisoft ODBC add any user security -- that is, application level, database level, table level, or column level security?
- How can I get column-level conflict checking in a replica set converted from Jet 3.x to Jet 4.0?
