by Two things. One not-so-serious, but a pain in the A--. The other was not a
big deal in my application, but I could see how it could be devastating for
others in certain situations.
Issue 1:
We run SQL Server 6.5 back end from Access 97 front end. In the beginning
we saw the usual update error issues on tables with text and/or image
columns ("another user has updated this record since you began editing
it..."). At the time the "fix" from MS was to add TimeStamp fields to all
affected tables. I was about to do this when MS released a Service Pack
(can't remember the number). Application of this SP seemed to clear up all
of the editing problems so I never bothered with the TimeStamp field
additions.
Well, the application of SP5a caused all of the problems to reappear and I
had to go in and add TimeStamps.
Issue 2:
I set up some of my tables to use the Numeric(10,0) datatype for the storage
of phone numbers. These all worked for many months just fine unitl the
application of SP5a combined with the new SQL Server ODBC driver (3.6) on
the client. Any entry of data in these fields would ALWAYS cause the final
digit to change by one (as if rounding were occurring). People using the
older (2.65) SQL Server driver would not experienc this problem and it was
confined to using MSAccess. The same edit done from within MSQuery would
store and display the proper number.
I rebuilt all of the tables using this datatype and changed them to varchar.
The nature of my application was such that it was immediately obvious that
the number was not stored properly. For someone else (particularly if the
data was a little more important than a phone number), I could envision that
this could have had serious consequences.
**** Posted from RemarQ - http://www.remarq.com - Discussions Start Here (tm) ****