Search results

Re: Could it be this bug in Access? Thanks, you've just saved me tons of time. :) It is working now, too, and it's exactly caused by switching over to ANSI-92.

The end result is that we needed to modify each Table on the SQL Server to add a new field (type Timestamp) called tStamp at the end of the record. Once that was in place, all of the problems went away. Thanks. I've been facing similar problem for a month now and avoiding it by different...