P
Patrick Tingen
Guest
Recently, we got a dataserver connection to a MSSQL database, so I thought that it would be a good idea to test my DataDigger against it. But either things have been set up wrong or I just don't get it. A short program shows me my databases: DEFINE VARIABLE iDatabase AS INTEGER NO-UNDO. DEFINE VARIABLE lSchemaHolder AS LOGICAL NO-UNDO FORMAT "Schemaholder/Sub-schema". CURRENT-WINDOW:WIDTH = 200. DO iDatabase = 1 TO NUM-DBS: IF SDBNAME(iDatabase) <> 'plshtest' THEN NEXT. lSchemaHolder = (SDBNAME(iDatabase) = LDBNAME(iDatabase)). DISPLAY LDBNAME(iDatabase) FORMAT 'X(8)' COLUMN-LABEL 'LDBNAME' SDBNAME(iDatabase) FORMAT 'X(8)' COLUMN-LABEL 'SDBNAME' lSchemaHolder COLUMN-LABEL 'Holder/Sub' DBTYPE(iDatabase) FORMAT 'X(8)' COLUMN-LABEL 'Type' WITH WIDTH 200 DOWN. DOWN. END. So plsh is my SQL database and plshtest my shemaholder. Suppose I would like to run a query against a table. If I run this: FIND FIRST plsh.progress_esb_message NO-ERROR. MESSAGE AVAILABLE plsh.progress_esb_message VIEW-AS ALERT-BOX INFO BUTTONS OK. It runs fine and tells me that - yes - there is a record found. Whereas when I do this: FIND FIRST plshtest.progress_esb_message NO-ERROR. MESSAGE AVAILABLE plshtest.progress_esb_message VIEW-AS ALERT-BOX INFO BUTTONS OK. I get this: Unknown or ambiguous table progress_esb_message. (725) ** Could not understand line 13. (196) I always thought I could run it against the 'progress' database, but it turns out that I cannot. Can somebody give me some insight?
Continue reading...
Continue reading...