At 05:00 PM 4/14/2008, you wrote:
Albert (and Razzak and John if you're listening),
I think I'm getting a reputation for being nuts since no one else
has commented. Believe me, I'm not making this up and I need an answer.
There are no temporary tables or views involved, and the problem is
not confined to one form or one table. All my forms relate to just
one table. My database is not rocket science.
I have finally been able to replicate the error and predict when
it's going to occur. This example does not mean that it's the only
circumstance that'll make it happen:
Locate a Variable Edit on a new or existing form.
Choose #DATE as the variable.
Make the font BOLD and save the form. It'll save just fine.
Now go back and make it REGULAR and here's a new wrinkle: The
little disk icon for saving REMAINS GRAYED OUT! When you RUN the
form with the little arrow, you get -ERROR- Disk problems,
etc. This happens in both 7.6 and 8.0. Toggle back and forth
between bold and regular a couple of times if necessary and watch
the disk icon. If you can't make it happen then I've got a serious
local problem.
This happens on not one but TWO computers. Someone please try to
replicate this. I'm willing to look like a jerk as long as I find
out what's going on.
Hello Fred,
The RBASE Users Group is not the main system to use for reporting bugs.
Although bringing those items up on the Users Group is a great way to
discuss workarounds for bugs, and the overall usefulness of feature
requests, there is a separate system set up for problem reports for
bugs and enhancement requests.
Those items should be reported through the R:BASE Developers' Corner Crew:
http://www.rbase.com/rbg7rdcc
There is a full bug and feature request reporting and tracking system
there. That's the fastest and most effective way to get the problems
corrected in production releases, as the R:BASE Development Team does
not automatically hear about the items reported here.
If necessary, you can email files that illustrate problems to
mailto:[EMAIL PROTECTED]
John
