Friday, March 9, 2012

Inserts not committing

A user entered 20 debit memos thru the application. For each db memo, 1 - th
e
data is inserted into two SQL Server 2000 tables, 2- a commit is issued
(Begin Trans / Commit Trans), 3 - a Select is used to retrieve data to
display on the db memo thru Crystal Reports and is printed. For each of the
20 entered, a db memo was printed but when the application closed, only data
for the first four db memos was saved / committed in the database. The other
16 had not been saved / committed in the database. We know the data for the
16 were inserted or else the Select would not have retrieved the data to
display and print the DB memo. There were no error messages and the
application did not crash. This happened only three times in 18 months and w
e
cannot duplicate the error. The commits are all processed in the same VB for
m
flow code. Anyone ever have a similar issue? Anyone have an idea on what
might have occurred? Thanx.Are you printing inside the transaction?
AMB
"Inserts not committing" wrote:

> A user entered 20 debit memos thru the application. For each db memo, 1 -
the
> data is inserted into two SQL Server 2000 tables, 2- a commit is issued
> (Begin Trans / Commit Trans), 3 - a Select is used to retrieve data to
> display on the db memo thru Crystal Reports and is printed. For each of th
e
> 20 entered, a db memo was printed but when the application closed, only da
ta
> for the first four db memos was saved / committed in the database. The oth
er
> 16 had not been saved / committed in the database. We know the data for th
e
> 16 were inserted or else the Select would not have retrieved the data to
> display and print the DB memo. There were no error messages and the
> application did not crash. This happened only three times in 18 months and
we
> cannot duplicate the error. The commits are all processed in the same VB f
orm
> flow code. Anyone ever have a similar issue? Anyone have an idea on what
> might have occurred? Thanx.

No comments:

Post a Comment