UpdateUsingStoredProcedures Error


Author
Message
Keith Chisarik
Keith Chisarik
StrataFrame VIP (1.6K reputation)StrataFrame VIP (1.6K reputation)StrataFrame VIP (1.6K reputation)StrataFrame VIP (1.6K reputation)StrataFrame VIP (1.6K reputation)StrataFrame VIP (1.6K reputation)StrataFrame VIP (1.6K reputation)StrataFrame VIP (1.6K reputation)StrataFrame VIP (1.6K reputation)
Group: StrataFrame Users
Posts: 939, Visits: 40K
I turned this on for all my BO's in an old project. When I go to update now I get the error that the update sproc tablename_UPDATE has provided too many parameters. The spoc on the server has a parameter count equal to the field count in the table. When I turn on debugging for the datasource I see it passing double the amount or parameters, one for easch field and one for each field with "_ORG" addd to the end?

Expected behavior? I have been working with DB2 so I dont have a lot of expereince using sprocs for my CRUD, I have it working but had to set the UpdateUsingStoredProcedures property back to false on the BO.

This was a small app that has to now grow so I think using CRUD sprocs is best, so I need to work this out.

Keith Chisarik

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search