Robert Willis wrote:
<snip>
I set up my ODBC correctly and the permissions are all OK but I need someway of getting all the tables over into Cache
Docs for $SYSTEM.SQL.Sybase():
/// Import a Sybase DDL/DML script file.<br>
/// The Sybase DDL/DML Import Utility supports the following statements:<ul>
/// <li>CREATE TABLE ...</li>
/// <li>CREATE VIEW ...</li>
/// <li>ALTER TABLE ...</li>
/// <li>CREATE INDEX ...</li>
/// <li>CREATE CLUSTERED INDEX ...</li>
/// <li>CREATE UNIQUE INDEX ...</li>
/// <li>INSERT ...</li>
/// <li>UPDATE ...</li>
/// <li>DELETE ...</li>
/// <li>SET OPTION ...</li>
/// <li>GRANT CONNECT ... (Same as Caché SQL CREATE USER ...)</li>
/// <li>GRANT { ALTER | SELECT | INSERT | UPDATE | DELETE | REFERENCES | ALL PRIVILEGES } ...</li>
/// </ul>
/// Statements other than the ones above are not handled by the utility and must be added
/// to your Caché application manually (if applicable).
(when I lonk tables it complains
about a filed having a reserved name)
Hopefully the above routine can cope
and then convincing the client
software that it is really accessing a Sybase or a SQL Server database.
That's a toughie: ODBC compatibility '= application compatibility.
Hopefully your Friendly Neighborhood Sales Engineer has a Sybase compatibility mode parameter for you... or one of the wiser ones from
this forum (help?)
Dave Y.
