I tried the command without continuation characters with no success - the error message still occurs. And the command works fine when the table is part of the database (not an SATTACH'ed table); this code has been running for a while now.
Maybe I'm screwing something up here. If you have any samples or docs that would be great. William Mason -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of A. Razzak Memon Sent: Wednesday, April 14, 2004 4:14 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: SCONNECT/SATTACH - Razzak's Reply At 03:52 PM 4/14/2004 -0700, William Mason wrote: >Using an SCONNECT'ed database, I get a error: "Number of select >statements for the server exceeded" has anyone encountered this? Only >seems to happen when the select is issued from a command file/eep. > >Statement is as follows: > >SELECT COUNT(*) INTO vciTestCount FROM CA_RSHistory WHERE InvoiceID = >.vctInvoiceID AND ControlNo IS NOT NULL AND RegistrationType IS NOT >NULL AND RegVoidInd = 'N' > >Runs okay from an R>. > >Also, has anyone succesfully used Rbase forms with an SATTACH'ed table? William, If the same statement runs okay at the R> prompt, then I would check the code used in command file or EEP, especially the continuing sign such as, '+'. Try the following: -- start SELECT COUNT(*) INTO vciTestCount INDIC ivciTestCount + FROM CA_RSHistory + WHERE InvoiceID = .vctInvoiceID AND ControlNo IS NOT NULL + AND RegistrationType IS NOT NULL AND RegVoidInd = 'N' RETURN -- End Assuming that the variable vctInvoiceID is defined, etc .. In reference to designing R:BASE Forms based on SATTACHed tables, the answer is YES YOU CAN! SATTACHed tables are treated as native R:BASE tables as long as the user(s) have the appropriate privileges, etc. The developer have to make sure that the server database(s)are SCONNECTed and all server table(s) are SATTACHed accordingly. Hope that helps! Let me know if you need more details or would like to see samples, etc. Very Best R:egards, Razzak.
