Here's a scenario that is problematic for me. I have db with tables: dbx.t1, dbx.t2, etc. I build an appfile that reference columns in these tables.
I now want to create another application that uses similar functionality, so I create a new database, with the same table names: dby.t1, dby.t2, etc. I create a new ODBC datasource for dby on the server and studio, then open up my appfile in the studio (Mac 5.09 or 5.5.0.5). Here are some issues I'd like help with. 1. When I open up my new dby datasource in the workspace I see all the dbx tables and all the dby tables!!! Clearly only the dby tables should be shown. 2. When I try the DataSource Select Tables menu, I almost invariably cannot remove the dbx tables. After setting it up to only use the dby tables, a DataSource Reload operation occurs, which then causes all dbx and dby tables to be displayed again. One time (out of about 80 attempts over several projects) I actually did get only the tables I wanted. But after quitting and restarting the Studio, they all reappear. And a few times I could delete some, but not all of the unwanted tables, and these unwanted ones would typically not reappear on reload. 3. The studio gets VERY confused about what tables should be used, rendering the Studio virtually useless for any search, update or insert action changes. Even after resetting a datasource for an action, the studio will reference dbx (the first listed) tables. In search actions, dragging a new column from dby, usually results in a join definition request. Likewise, update and insert actions can't be modified, because the Studio thinks there are different databases involved. 4. Editing the xml by hand is usually the only answer. A global replace of 'dbx.' with 'dby.' is needed to make these things work. But subsequent modification in the studio can still break things. 5. Interestingly, removing all references to dbx or dby in the XML file, (eg., changing dbx.t1.id to t1.id) and then opening up the file in the studio, will cause some actions to reference dbx and some to reference dby! Maybe there is a simple work around. But it seems to me that the only way to avoid these problems is to delete the other datasources from the Studio, so you are only working with one at a time. Needless to say, all of these issues remove much of Rapidity from the RAD environment. Does anyone have any suggestions? (Max OSX.2.8, OpenLink MySQL, various studios). P.S., the server does NOT get confused about which data source to use, as long as you have the right database name in the taf file. Bill Conlon To the Point 345 California Avenue Suite 2 Palo Alto, CA 94306 office: 650.327.2175 fax: 650.329.8335 mobile: 650.906.9929 e-mail: mailto:[EMAIL PROTECTED] web: http://www.tothept.com ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
