I believe I got this now. I missed setting the DataSourceKey for each Business Object. This wasn't pointing to the correct data source.



Thanks for the help.

Trent,



This may be a more telling of what my issue is. I have a stored proc to retrieve my data for the BO. The BO object is pointing at a table in my production dB. In debugging, when this stored proc is called, my SqlCommand variable has a ConnectionString as follows:



"Data Source=mycomputername\\SQLEXPRESS;Initial Catalog=StrataFrame;Integrated Security=True;Persist Security Info=False;Asynchronous Processing=True"



This has to be the underlying issue. But why would this be pointing at the StrataFrame dB?



Thanks,

Doug.

No, it relates to the DataSourceKey setup on the BO.  I would highly recommend reading through the help as all of this is outlined.  It would probably clear some of this up instead of little segments coming from me.

Does the naming of the data connections relate to the Project Names set up on the BOM?

Well, this SetDataSources method is where you should be setting up the data sources for your BOs at runtime.  You can technically setup the DataSources anywhere prior to actually calling a query on a BO, but the SetDataSources method is where you define all of your connections that will be used at run-time by the BOs.

Trent,



Another naive question. How does the SetDataSources method in Program.cs relate to the data connections for the Business Objects (if there is a relation at all)?



Thanks,

Doug.

Doug, that is the direction I would go.  This whole episode has seemed a bit strange anyway.  I cannot even think of what could be causing it past the things mentioned in previous posts.

Trent,



I was attempting to create a sample app and dB (rather than send my production code), and for some reason or other, it works (I don't need to qualify my stored procs or table names). I don't think I did anything different.



If I were to create a new project for my BO's and copy my existing BO's to this project, then re-build everything once I've defined the project's properties in the Mapper, could this potentially clean up something I've done? Or is this more a factor of the entire solution?



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.

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.