ADP - Form Edit

  • Thread starter Thread starter stuartb113 via AccessMonster.com
  • Start date Start date
S

stuartb113 via AccessMonster.com

I have a form bound to a SQL Server stored proc. The stored procedure links
2 tables, both of which have a unique index. I have set the unique table
property of the form to be the table to be updated or have rows inserted -
this is the many join relationship of the select query of the stored
procedure.
When add a new record the following Microsoft Access msg is returned:

The data was added to the database but data won't be displayed in the form
because it doesnt satisfy the criteria in the underlying record source

has anyone experienced this before?

thanks,
Stuart
 
Try adding a resync command.

Using SQL-Server Profiler will give you the info you need to see what's
happening between Access and SQL-Server.
 
Profiler was useful to see what was going on but hasnt helped in providing an
answer.
The resync command helps to a point in the entered record is now saved but on
adding the new row, Access returns the following message which I cannot roll
out to the users!

msg: Multiple-step OLE DB operation generated erros. Check each OLE DB
status value, if available. No work was done

Note: the update and delete record operation works perfectly

Sylvain said:
Try adding a resync command.

Using SQL-Server Profiler will give you the info you need to see what's
happening between Access and SQL-Server.
I have a form bound to a SQL Server stored proc. The stored procedure
links
[quoted text clipped - 11 lines]
thanks,
Stuart
 
Stuart,

Perhaps the data you entered in fact does not satisfy the underlying record source.

That can happen when you have a (server)filter on the form and the record just added doesn't pass the filter.

Do you have a filter?

This can also happen if your stored proc returns an equijoin between the two tables, becuase, since you only added data to the
'unique' table, it is unrelated to any row in the non-unique table and so won't be returned by the equijoin.

Do you have an equijoin?

Show us the stored proc!

Tell us what data you entered which got saved and then generated this message!

Cheers,

Malcolm Cook
Stowers Institute for Medical Research - Kansas City, MO USA
 
Hum, they are many things that can bring a Multi-step errors. I've seen
this message myself many times in the past but I can remember under what
kind of circonstances exactly this occured.

Any trigger on the SQL-Server side?

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF


stuartb113 via AccessMonster.com said:
Profiler was useful to see what was going on but hasnt helped in providing
an
answer.
The resync command helps to a point in the entered record is now saved but
on
adding the new row, Access returns the following message which I cannot
roll
out to the users!

msg: Multiple-step OLE DB operation generated erros. Check each OLE DB
status value, if available. No work was done

Note: the update and delete record operation works perfectly

Sylvain said:
Try adding a resync command.

Using SQL-Server Profiler will give you the info you need to see what's
happening between Access and SQL-Server.
I have a form bound to a SQL Server stored proc. The stored procedure
links
[quoted text clipped - 11 lines]
thanks,
Stuart
 
why dont't you just RunSql 'Update myTable set myfield = 4 where
myrecordid = 23455'

those never fail.

but did you set the 'unique table' property??

i get THIS

The data was added to the database but data won't be displayed in the
form
because it doesnt satisfy the criteria in the underlying record source


ALLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL the time.
i mean--

you have a view

'select * from orders where orderDate > getdate()-20'

you add a new record to this view with an orderDate from 5 months ago
and you'll see this message.

i've never had a problem with this piece; works just as intended.
 
Back
Top