For now, we did end up going with something similar to what Fred Grooms proposed. One of the DBAs suggested changing the "int" data type to "bigint". Since there isn't an actual "T" table in ARSystem for a view form, we created one, and then changed "int" to "bigint". So far, everything's working like it should.
Ultimately I was able to replicate the problem on another machine by restoring from a backup and re-installing the AR System software. I figured out where to change the collation method in SQL, at least for an individual database (not for the entire server). I changed this to "Latin1_General_CI_AI" (which I'm now told is the default), but this by itself does not fix the problem. It may be just another symptom of whatever it is that happened - we still don't have the root cause. Thanks to Fred and to Joe Desouza for their input! Have a good weekend, Bill Bookers On Fri, 21 Nov 2008 09:58:31 -0600, Grooms, Frederick W < [EMAIL PROTECTED]> wrote: >Out of curiosity ... You said in an earlier message the Database Input Length was 4 on the form for that column. >What happens when you change it to 5 (or 15)? > >Fred _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
