v9 Business Object / Table / Editable not working

Brian Echard

II want to create a simple editable grid from a table that is listed under Solution Tables.  When I go to create the Business Object it works if I use a query but not if I choose table.  It says the table doesn't exist.  I know it exists because when i do a simple query object it works great.  I also verified the table in SQL app.  I am still investigating but can't see why it lists all the std tables but none of the other tables for the process that are listed under solution tables.

Brian Echard

I figured it out.  We have a three tier architecture.  DEV, TEST, & PROD.  In the designer when I go to business objects it is querying dev for tables that exist even though I was publishing to TEST.  I would think it would use the connection info from the drop down in the menu bar but apparently not.

Jerome_Pearce

This is one of the main reasons we do not like, or indeed, recommend, having one Designer deploy to more than one server. The need to fully understand the configuration, and the implications of changes to each database and the effect on the Designer itself, as opposed to the 'application' only, makes it awkward and prone to error.

 

The need to have the database connection has always been in the product, and that has been (fairly) OK up until version 9, although there can still be problems. In version 9, abstracting out the deployment layer as a service, although a great idea, has made the deployment and database separate. This is a central area for massive confusion along the lines that you have experienced. Not only that, but the very, very serious problems that plagued the DataSet control in previous versions (namely faults occurring if the schema was even slightly different in each database) will almost certainly appear in this scenario with Table Business Objects.The reasons will be exactly the same - that we are unable to specify the field order when selecting the fields returned for this Business Object type. Query Business Objects will not suffer the same problems.

 

I have yet to test this, as changing databases is no longer a simple operation (as I have documented too), or even something we recommend doing at all any more.