Re: Error 3155- Is there no solution?

Hello Gordon,

This has a SQL Server backend, I'm not sure of the version, maybe 7. Access
2000 is the front end. There are about 12 workstations on site in western
NY and maybe 4 or 5 remote users in Tn. This particular function, Order
Entry, usually has only two users in NY and I don't know how many input
remotely, at least 2.

I can reproduce the error with only myself on the whole system. I don't
know about bandwidth. This is a lan with outside access using terminal
server.


"gllincoln" <gllincoln@xxxxxxxx> wrote in message
news:01943262-DCA9-407D-A17F-258EA06F3E12@xxxxxxxxxxxxxxxx
Hi Mark,

How many concurrent users - what are the chances of collisions? What kind
of locking? What is the back end - SQL? Access? How much server traffic
is there? How is the bandwidth?

Gordon


"Mark A. Sam" <MarkASam@xxxxxxxxxxx> wrote in message
news:ektjUwkdIHA.4744@xxxxxxxxxxxxxxxxxxxxxxx
Hello,

I am getting Error 3155- ODBC--insert on a linked table 'Order Entry ST
Material' Failed.

There are two tables I am popluating using DAO Addnew/Update methods. On
is a Materials table the other a Tasks table. The originating data is
from local tables. The Error comes after the Update method.

I have done a search on this error and there are hundreds of result
dating back from at least year 1999, and noone seems to have a solution
other then the possible reasons, which don't apply to my situation. The
Tasks table always populates without a problem. The Materials table is
the problem where it sometimes populates and sometimes bombs out. There
doesn't seem to be any discernable pattern. It bombs out when it does.

That Tasks and Materials are related to different Products. It mostly
bombs out for a particular product called a Spot ***, but sometimes it
will happen with all of the products on an order.

If an order is entered, however, and the database closed and reopened or
the user switches to another record and returns, then the problem doesn't
occur.

Any help on how to solve this would be apprecated.

Thank you and God Bless,

Mark A. Sam





.