Business Object SAVE() and Stored Procedures


Author
Message
StrataFrame Team
S
StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)
Group: StrataFrame Developers
Posts: 3K, Visits: 2.5K
is this a stored procedure that you created, or is it one that the DDT created?
Clayton Hoyt
Clayton Hoyt
StrataFrame Novice (66 reputation)StrataFrame Novice (66 reputation)StrataFrame Novice (66 reputation)StrataFrame Novice (66 reputation)StrataFrame Novice (66 reputation)StrataFrame Novice (66 reputation)StrataFrame Novice (66 reputation)StrataFrame Novice (66 reputation)StrataFrame Novice (66 reputation)
Group: Forum Members
Posts: 40, Visits: 85
Its a sproc I created. What would be the difference?
StrataFrame Team
S
StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)
Group: StrataFrame Developers
Posts: 3K, Visits: 2.5K
The business object is expecting a certain structure for the stored procedures.  The structure depends upon the UpdateConcurrencyType that you have configured.  In the DDT help file, under Tables -> Table CRUD Stored Procedures, you will find examples of the stored procedures that the business object is expecting.  Most likely, you still have the UpdateConcurrencyType set to OptimisticAllFields, which is the default.  If that is the case, the business object is expecting to send all of the fields twice so that it can check the concurrency before it does the actual update.  Your best bet is going to be to set the concurrency to OptimisticRowVersion, which means you will need to add a row version column to your table or just set the concurrency to Off, which won't send any extra fields in the update.
StrataFrame Team
S
StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)
Group: StrataFrame Developers
Posts: 3K, Visits: 2.5K
Also, in your AppMain.vb, at the bottom of the SetDataSources() method, you can call this:

DataBasics.DataSources("").SetDebugOn("C:\Debug.html", True)

This will turn debugging on on your data source and create that Debug.html file containing a list of the DbCommands that were executed against the data source.  It will list off all of the parameters, so, you can get a better picture of what the business object is expecting for the signsture of the stored procedure.

I believe it will also automatically show the debug file when the application exits it it exits logically.

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