Regardless of whether you link the tables via the gateway or import the
tables you'll hit the same problem when compiling the table: Cach� Sql is
far stricter about sql reserved words than its Rdbms competitors. There is
an easy way of dealing with it: simply delete the offending field or table
name from Cach�'s list of reserved words in global
^%qCacheSQL("reservewords") in namespace %Cachelib. I dare say this is not
an officially endorsed solution but I've never experienced any subsequent
problems.(Btw: Little snag when linking tables via the SQL Manager: Cach� will create the class and then error on the table compilation. You won't see the table in SqlManager but the class definition is saved and you'll have to remove it before you can try to link again). Wolf Koelling Slaughter and May "Robert Willis" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > I have an Asset Management System that runs slowly on my local Sybase system > or MS SQL Server > > I would like to run it from a Cache Server but the client-end seems to be > able to recognise what server it is accessing to get the data from. > > I set up my ODBC correctly and the permissions are all OK but I need someway > of getting all the tables over into Cache (when I lonk tables it complains > about a filed having a reserved name) and then convincing the client > software that it is really accessing a Sybase or a SQL Server database. > > Any suggestions? > > >
