Golly bee,
What a relief, just about to call the state for help. Thinking also
that it maybe the heat had gotten to me.
Because it was "WHE" I was thinking that it RBase was looking that the
WHE stood for the command Where, but, I tried several other short forms
of commands, and that blew my thought out. So I doubt that, that would
be the problem.
Got to get some more responses before it becomes a bug. Note: bug
chasing was a large part of my life in former years so I am hesitant and
careful before submission.
Thanks Dawn and Sami,
Ken
--
Reclaim Your Inbox and your sanity!
For Mail Choose: http://www.mozilla.org/products/thunderbird/
For A Browser Choose: http://www.mozilla.org/products/firefox/
Get them, they work for you....
<>< = = = = = = = = = = = = K ~ V ~ T = = = = = = = = = = = = = = = ><>
Dawn Oakes wrote:
I second that vote!
-----Original Message-----
From: Sami Aaron [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 27, 2006 3:25 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Syntax Error - 2367
Are we still having fun? I just tried it in one of my client's
databases and it won't even let me save 'whe' the first time. That's in
the browser.
When I try to do an update at the R> Prompt to set the value in a text
field to 'whe', I get the error message "columnname must be a valid TEXT
(122)"
update notions set columnx = 'yyy' where columnx = 'xxx' WORKS
update notions set columnx = 'whe' where columnx = 'yyy' ERRORS
I vote that Ken submits it as a bug!
Sami
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Dawn
Oakes
Sent: Thursday, July 27, 2006 2:08 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Syntax Error - 2367
Sami
Actually, I just tried using RRBYW10 and was able to replicate it.
Still don't know if it's a system (cfg) thing or something else. Try
it.
-Enter a new row in any table with a text column. (I used PrintOptions)
-In the text column, enter whe (I used DisplayName) -Leave the row,
thereby saving it, enter the row again and try to change the whe to WHE.
I also tried changing previously entered rows in the table. (I tried to
change XLS File to whe and had the error.)
Dawn
-----Original Message-----
From: Sami Aaron [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 27, 2006 2:46 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Syntax Error - 2367
Ken -
It almost sounds like you have a corrupted rule in that table or
corruption in the database itself. Type LIST RULES FOR <youtablename>
and see if there are any and if so, if they look to be correct.
If there is a rule, try dropping it and adding it back in.
Otherwise, I'd UNLOAD/RELOAD the database and look for errors as you do
that.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sami Aaron
Software Management Specialists
913-915-1971
[EMAIL PROTECTED]
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Ken
Tooker
Sent: Thursday, July 27, 2006 1:24 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Syntax Error - 2367
Oma,
Try your sample again, but I can enter the "WHE" once, but cannot change
it. It will take the entry the first time say for example "WHE" but
when for example you wanted to change it to"whe". Now I get the syntax
error 2367.
Again, thanks,
Ken
--
Reclaim Your Inbox and your sanity!
For Mail Choose: http://www.mozilla.org/products/thunderbird/
For A Browser Choose: http://www.mozilla.org/products/firefox/
Get them, they work for you....
<>< = = = = = = = = = = = = K ~ V ~ T = = = = = = = = = = = = = = = ><>
Ken Tooker wrote:
Oma,
Thanks for the response. And I figured it had to be something that is
here local in my office as well at my customers site.
But, I did create a new database not using a full blown database one
from a fresh start using Version 7.1. Also, with the same names that
you had. "test" for the database name and "test" for the table.
However, in real life and offsite, the names are different. It
appears that this did not matter. But, (here I go with my buts) the
table that I created I did was within the same directory as my problem
database.
Proceed on, I just created a new directory, nothing else in it, then
created a new database. Like you found, the problem is *_not_* there.
It has something to do with the original database I have to assume.
Now what to look for is another treasure hunt. I persevere... :-[
Thanks, I will keep you posted..
Ken
