>These are not necessarily in order. Couldn't resist after struggling with an update today..this applies to 6.5...
>
>1. Blank dates in the client-side data.
>2. Identity fields and @@IDENTITY.
>3. DBAs who don't synchronize test and production databases.
>4. ODBC 254-character command limit.
>5. Any =SQLEXEC() returned value of -1
>6. Forgetting to SQLDISCONNECT()
>7. "Executing remote...."
>8. Timestamp fields.
>9. Transaction logs in test environment.
>10. Did I mention blank dates? Blank Dates!! (Deserves two).
I agree that Blank dates are a pain. I usually have to check for 01/01/1900 and .null. for a blank date. Which brings me to the one PITA you forgot -- NULLs!
I don't use Indentity or Timestamp fields. I have a table to store all the counters and have moved it to the server.
Another thing I do with SQLEXEC() returning -1 is:
lnresult = SQLEXEC()
if lnresult < 0
error message()
endif
The ERROR command allows me to suspend and see what is going on with the debugger.
