[RBG7-L] - RE: Application question

[Sami Aaron]

Dick -   I think you're correct, within an RBA file.  But here are a couple more options:   1. you could launch a second RBA file that's connected to the other database 2.  you could set the archive database up as an ODBC data source (or use a DSN-less connection) and connect to the tables from the live database - type HELP SCONNECT at the R>Prompt to see the syntax   Sami From: rbg7-l@rbase.com [mailto:[EMAIL PROTECTED] On Behalf Of Gunnar Ekblad Sent: Wednesday, December 29, 2004 10:25 AM To: RBG7-L Mailing List Subject: [RBG7-L] - RE: Application question Dick A long time ago I had the same issue. That�s why I stopped using RBA in favour of a form driven menu that acts on Exit variables closing the form and return to my startup file opening and closing databases at my will. On the other hand if I recall correctly Razzak has previously explained how that can be done! So hang in there if you want to stay in RBA I believe you can but my preference is still not to use RBA   Gunnar Ekblad   -----Original Message----- From: rbg7-l@rbase.com [mailto:[EMAIL PROTECTED] On Behalf Of Dick Fey Sent: den 29 december 2004 16:43 To: RBG7-L Mailing List Subject: [RBG7-L] - Application question   Before I waste any more time on this...   Am I correct that if you are running an RBA application   You can NOT disconnect and connect to any other database, then return as you could in 6.5++   I switch db;s to look at archived data.  If I run the file outside the app, it runs perfectly, but inside the app it gives me an illegal command in eep error.   Dick Fey