Gunnar and all, Found it. As usual it was the space between the ears of the programmer. Had not declared a variable so it was erroring. The disturbing thing I have to figure out now is that I call a form action to clear all the variables before and after every process so I am not sure why the offending variable was in the way.
Jan -----Original Message----- From: "Gunnar Ekblad" <[EMAIL PROTECTED]> To: [email protected] (RBASE-L Mailing List) Date: Wed, 3 Sep 2008 20:07:54 +0200 Subject: [RBASE-L] - Re: DB settings Jan I am at los here but have you tried *variable? ----- Original Message ----- From: jan johansen To: RBASE-L Mailing List Sent: Wednesday, September 03, 2008 7:40 PM Subject: [RBASE-L] - Re: DB settings Gunnar, This particular client will not allow me to change these settings which has prevented me from doing things like SCONNECT. My problem I'm facing now is that I have a process that if they do it first works fine but if they do another process first and then try the first one they get error messages. All variables are cleared prior to each process so the only thing I have found so far is that I pass a parameter in a custom form action that includes the %variable. Jan -----Original Message----- From: "Gunnar Ekblad" <[EMAIL PROTECTED]> To: [email protected] (RBASE-L Mailing List) Date: Wed, 3 Sep 2008 19:32:16 +0200 Subject: [RBASE-L] - Re: DB settings Jan My best guess is that you should stick to many as % I myself are totaly converted to many as % I know it was a pain in the beginning but nowdays I will not consider to go back ----- Original Message ----- From: jan johansen To: RBASE-L Mailing List Sent: Wednesday, September 03, 2008 7:22 PM Subject: [RBASE-L] - DB settings I'm trying to track down a very weird problem. Will having the MANY set to * affect %variables? Jan
