Cannot update items in table through Syseditor (OpenInsight Specific)
At 14 SEP 1998 03:21:25PM bc wrote:
How can I unlock a table that the syseditor and a bound form will not update too?
The dos attributes are set ok and and I am on a single workstation not connected to any network. The table reads fine and does not
have any errors (GFE etc.) when verified.
Thanks
At 15 SEP 1998 09:57AM Blaise(Revelation) wrote:
Bruce,
Can you verify the table is locked? What happens when to try to
update the table? Do you get any errors?
Let me know if you get a chance.
Blaise
At 15 SEP 1998 09:57AM Aaron Kaplan wrote:
What sort of error is it giving, if it's giving one at all?
Can you write from code? What is in @FILE.ERROR and returned from GET_STATUS after the write?
At 15 SEP 1998 04:52PM BC wrote:
I am not getting any error msg's that I can see. I do see a little
…locked… msg on the status line of the syseditor when I go to save
the record. I am wondering about my indexes and such. Any thoughts?
Bruce
At 15 SEP 1998 08:00PM Andrew P McAuley wrote:
Is it a dictionary table?
World Leaders in all things RevSoft
At 16 SEP 1998 01:31PM bc wrote:
It is a standard LH table. With a dict and data portion.
At 16 SEP 1998 02:29PM Andrew P McAuley wrote:
Sorry - are you updating the data or the dict?
At 16 SEP 1998 10:34PM bc wrote:
Andrew,
The data. If I open a record through the syseditor, change/add
an attribute then open again the changes are not there. Hence, no update/write. I am hesitant to 'manually' remove the indexes at this time and would like to now how the system processes files during an update. Is it/it is possible that a 'control' record is messed up.?!
BC
At 17 SEP 1998 01:58AM Andrew P McAuley wrote:
If you write a program to do the write is there a value in @file.error after the write?
World Leaders in all things RevSoft
At 18 SEP 1998 10:37AM bc wrote:
Regarding File.Error variable.
No value, it is null. File.Error.Mode=0
File.Error='
File.Error.Mode=0'
File_Error='
File_Error_Mode=0'
"I'm so confused…"
At 21 SEP 1998 07:36AM Cameron Revelation wrote:
bc,
To see the file error, use the MSG function:
Msg(@window, "error#": @file.error)
Cameron Purdy
Revelation Software