[ic] read only tables problem, where is this set??
Sun, 12 Nov 2000 06:16:50 -0500
I've posted I'm using SQL, and the problem is with the read-only in-memory
tables which are not stored in the SQL database, and which the program is
insisting are _read_only_ on disk. I've posted the error messages from the
These are the tables that you edit the variables, such as address, or phone
numbe,r or company name, or password, then "apply changes".
I would buy your answer _except_ that the logon generates the same error,
and that _is_ undeniably, an error condition that has generalized beyond
"in memory" tables not being able to be written to directly (their disk
counter part _SHOULD_ be writeable).
A private reply is being sent to you.
Robert S. Pataki, MD
President, PUGDOG Enterprises, Inc.
PUGDOG® and Digital Postcards® are Registered Trademarks of PUGDOG
At 08:17 AM 11/11/00, you wrote:
>Quoting Pugdog (email@example.com):
> > Mike,
> > I'm not an idiot. The editor is there to allow editing of that table,
> > the changes
> > are APPLIED when the server is restarted.
> > If this table cannot be edited, then why is there an option to edit it?
> > Also, if this table cannot be edited when the server is running, why can
> > you edit
> > the file in a text editor, apply the changes, and continue.
> > If this _WAS_ documented I would not have asked.
>It is documented in the reference. You can edit the table, it just won't
>work on the fly.
>You can believe me or not as you choose.
>The fact is, a DBM is required or SQL is if you want to have editable
>data that doesn't require a restart. Perhaps I should put one of
>those big red warnings on the menu page.
>Akopia, Inc., 131 Willow Lane, Floor 2, Oxford, OH 45056
>phone +1.513.523.7621 fax 7501 <firstname.lastname@example.org>
>Research is what I'm doing when I don't know what I'm doing.
>-- Wernher Von Braun
>Interchange-users mailing list