RE: [RBASE-L] - how to eliminate this error

2017-04-04 Thread Dan Goldberg
CONNECT dbname SET ERROR MESSAGE 2495 ON ENDIF Dan Goldberg From: rbase-l@googlegroups.com [mailto:rbase-l@googlegroups.com] On Behalf Of MOHAMMED SATTAR Sent: Monday, April 3, 2017 9:02 PM To: rbase-l@googlegroups.com Subject: Re: [RBASE-L] - how to eliminate this error I am also getting

Re: [RBASE-L] - how to eliminate this error

2017-04-03 Thread MOHAMMED SATTAR
I am also getting the below sometimes but haven’t been able to figure out why … first i thought it could be due to system unable to make scratch or $$$ files in time but that is not the issue any answers willed be welcome Mohammed Sattar Utah Group Bangladesh > On Mar 31, 2017, at 7:54 PM, Dan Go

RE: [RBASE-L] - how to eliminate this error

2017-03-31 Thread Dan Goldberg
: rbase-l@googlegroups.com Subject: Re: [RBASE-L] - how to eliminate this error I have never heard of SQLCODE = -7. My goto is: SET VAR vtext = (CVAL('Database')) IF vtext IS NULL THEN PAUSE 2 USING 'Trouble Connecting to Database!' CAPTION 'ERROR!' + ICON ST

Re: [RBASE-L] - how to eliminate this error

2017-03-31 Thread karentellef via RBASE-L
s to happen for you, maybe try replacing the SQLCODE with a test of a connected database as above? Karen -Original Message- From: Dan Goldberg To: rbase-l Sent: Fri, Mar 31, 2017 9:25 am Subject: RE: [RBASE-L] - how to eliminate this error I use his startup stuff except this part

RE: [RBASE-L] - how to eliminate this error

2017-03-31 Thread Dan Goldberg
] - how to eliminate this error I use Razz's config setup in all my compiled apps, that enforces multi on Tom On Mar 31, 2017 8:54 AM, "Dan Goldberg" mailto:d...@lancecamper.com>> wrote: Sometimes when we run our compiled apps we get this message. [cid:image001.png@01D2A9EE.

Re: [RBASE-L] - how to eliminate this error

2017-03-31 Thread Tom Hart
I use Razz's config setup in all my compiled apps, that enforces multi on Tom On Mar 31, 2017 8:54 AM, "Dan Goldberg" wrote: > Sometimes when we run our compiled apps we get this message. > > > > > > If we exit and run it again it works fine. Just annoying. It is a link on > our desktops to ou