Hi,



I'm in the process of determining which data update method I'd like to utilize, and have come across a little confusion. I've set up a table, and have a select, insert and update stored procedure (labelled like tablename_Insert as per recommendations). I have a business object which connects to said table. I've put the BO onto a form, and have a save function on the form. I set the BO property InsertUsingStoredProcedure to true. When I perform a save, the system reports an error with the message that it cannot locate the stored procedure named dbo.tablename_Insert.



However, if I qualify the BO on the form by setting the InsertStoredProcedureName to databasename.dbo.tablename_Insert, the save functionality works.



Any ideas?



Thanks,

Doug.

Hi Doug,

Just a stab in the dark - I would be double checking the BO Mapper to make sure you have an Initial Catalog in the connection string.

Cheers, Peter

I would double check your names.  The default naming schema expected (if not provided) is like you mentioned, TableName_Update, for example.  So if this is not being found, then I would wonder if your schema name or initial catalog (like Peter mentioned) does not line up with the sproc name.  If you want to see this in action, I would recommend letting the DDT create one of these for you and then you would see exactly how it is defined.

Both my procedure naming convention and the initial catalog appear to be correct. Attached is my Business Object Property dialog. I have attempted selecting as source both the SQL Server and Database Deployment Toolkit options.



I have also attempted manually added the connection string. Are there any differences in using SQL Server Express?



Thanks.

Doug.

Doug,

Like Peter and Trent suggest, double check the connection string in the BOM Project Properties form, when you select your SQLExpress server, the connection string should have the "Initial Catalog=" like the sample below of one of my projects:

Edhy Rijo

I've got a really naive question, but being a newbie to SF, I hope I'm forgiven. What's worse, I know exactly what you are talking about in the Connection string.



My issue is how do I see the connection string in the Business Object Mapper? I can see that the structure has a selected Class, Database, Table and Schema. But I see nowhere that I can view the connection string, other than the Connection String Override.



Help?

Hi Doug,

Nothing to worry about being newbie

To see the connection string do the following:

1. Open the BOM
2. Select your BO Library Project
3. Click the "Modify Project Properties" link on the right pane
4. You will have the Project Properties form which has the SQL Server Connection String as below:

Edhy Rijo

OK. Thanks.



My connection string is as follows:

Data Source="my computer name"\SQLEXPRESS;Initial Catalog=TPCShip;Integrated Security=True;Persist Security Info=False;Asynchronous Processing=True



The only difference between the example and mine is that I have a "named" Data Source, and my Default Structure Settings is set to SQL Server rather than Database Deployment Toolkit. My Initial Catalog is set (which I presume is correct, since that is the database I want to hit).



Is there anything else I should be looking for?

I just noticed something else that may be causing my issues. I just created a new BO, and upon specifying the BO properties, I noticed that my previous BO's did not have a Profile specified.



What is this for and if this is in fact an issue, how do I get my original BO's to obtain the Profile?



Thanks,

Doug.

I assume that you are referring to the BO Mapper.  In which case, this is remember by project.  So if you have BOs in a solution/project named Doug.Zapp.Business, then you would create a BO Mapper project this assembly.  If you create a new solution or move the project into a new solution, that is fine, just select the exiting BO Mapper project instead of creating a new one.

All of the issues you are fighting here sound really strange.  You are welcome to post a sample with a database and simple project showing your issue and then we could go from there if this doesn't get you going as the run-time issue you are fighting is going to be unrelated to the design-time.