Re: Access to Other ODBC database -Reply

I apologise if this has already been offered as I haven't been following the thread. Unfortunately it doesn't seem possible to do a data definition query to rename the attribute names, so this is about the only way I can think of to do it, but it should work. Attach the tables from the odbc database to an Access database normally. They will attch with the owner name as prefix.(EG Mytable becomes tashkop_MyTable) Build a query on each attached table to alias the attribute names to the long version that Access wants to use. Name the queries to the original table name that the application expects (EG MyTable) example as under (Query is named MyTable): SELECT DISTINCTROW tashkop_MyTable.wr_id AS [My Work Request],tashkop_MyTable..date_code AS [The Date Code], tashkop_MyTable.date_value AS [The Real Date] FROM tashkop_MyTable; HTH rgds Peter Tashkoff <tashkop@zespri.co.nz> Project Consultant/DBA Zespri International Limited. This posting may not be used by any party for the vilification of any other. >>> Simon Ellison-Bunce <simonb@misslink.demon.co.uk> 11/March/1997 12:55am >>> >Rick Duff <rduff@asacomp.com> wrote in article ><01bc2994$fa3ef5a0$2588b2c7@rduff>... >> I need to know if there is a database program out there >> (along the lines of Oracle, SQL Server, Sybase, etc..) >> that can handle table and field names with spaces in >> them like ACCESS does. I need to migrate an >> application to another database that we don't have the >> source code to. In article <01bc2a98$0c3ef760$ba6be6cd@eagle>, Jim Reineri <jreineri@atlcom.net> writes >Do yourself a big favor. >Byte the bullit and remove the spaces and special characters from your >column names right now. If Rick doesn't have the source code to the application, then a) removing the spaces from his field names is just going to break the application, and b) this is going to be just about impossible to do in any case. -- Simon Bunce SHL Learning Technologies