Re: Inconsistencies while inserting data into a Database -

["Barnes, Tracy" <TBarnes@CIBER.COM>]

The problem is with your ODBC drivers.

If you are running SQL Server 2000 with SQL Server 2000 Service Pack 1
loaded on the server, then all of your client machines that will be using
2-tier access into the database needs to have updated ODBC drivers.

These can be downloaded from Microsoft's support site.  If you look for MDAC
v2.6 (Microsoft Data Access Components), you should find what you need.
This must be done on each Windows machine running SQR's on the client, or
logging in 2-tier.

Hope this helps!

-----Original Message-----
From: Sandquist, Ray [mailto:raymond.sandquist@TRINCOLL.EDU]
Sent: Thursday, February 21, 2002 9:11 AM
To: SQR-USERS@list.iex.net
Subject: Inconsistencies while inserting data into a Database -


Hi All,

I have recently come across some data inconsistencies while performing
inserts into a SQL database using SQR and was hoping someone might have some
insight.

The Facts: We are currently using SQR Version 4.3.4 against SQL server 2000
running in 7.0 compatibility mode. (we've just upgraded from version 7.0 SQL
server) (The database is PeopleSoft HR Student Admin ver 7.6)

While inserting data into a table some of the data values are getting
truncated. A show statement in the SQR shows the correct value that should
be inserted.  For example:

If I insert 5 rows of data:                             The end results
might be:

row 1  value ABC                                ABC
row 2  value AB                                 A
row 3  value ABC                                A
row 4  value AB                                 AB
row 5  value AB                                 A

This problem is not unique to a specific program, and is inconsistent when
it does occur (if I truncate the data and reload, it is not the same set of
records that are getting truncated.) Has anyone ever experienced a similar
problem? Are there any compatibility issues with SQR 4.3.4 and SQL 2000? Or
with SQL 2000 running in a compatibility mode, that anyone is aware of?

I appreciate any and all responses.


Thanks

Ray Sandquist
Application/Programmer Analyst
Trinity College
Hartford,  CT 06106-3100