Datamodule error: "..already a database open .."

I use the newest version of fdBase 

The following problem seems to be limited to datamodules were more than  rowset
is involved and where parent-child links exist.

When writing code for an event for a rowset and closing the text window, I get
the following error message:

"There is already a datamodule open in dQuery.  Save before closing?"

If I say "Yes", I get an even bigger error message and I end up with a
blank datamodule screen.

All "active = true" statements in the code has disappeared!  If I
re-enter the "active = true" statements, then I get what I expect to
see, i.e. the database and all rowsets placed in the datamodule has returned,
but as expected. all parent-child linkages are now gone.  These then need to be
rebuilt.

I can minimize loss by pressing ctrl-s after making changes to the code, then
responding "No" when the first error message appears.  When following
this route, the parent-child links sometimes disappears.

When all required coding has been done, I close the datamodule, re-open it and
then rebuild the parent-child links.

Surely the above is not normal, I have not encountered it with previous versions
of dBase.  Has anyone else had a similar experience, and how does one prevent
this from happening?

In article <17zpFhkfHHA.528@news-server>, psvh@mweb.co.za says...
> I use the newest version of fdBase 
> 
> The following problem seems to be limited to datamodules were more than 
rowset is involved and where parent-child links exist.
> 
> When writing code for an event for a rowset and closing the text window, I
get the following error message:
> 
> "There is already a datamodule open in dQuery.  Save before
closing?"
> 
> If I say "Yes", I get an even bigger error message and I end up
with a blank datamodule screen.
> 
> All "active = true" statements in the code has disappeared!  If I
re-enter the "active = true" statements, then I get what I expect to
see, i.e. the database and all rowsets placed in the datamodule has returned,
but as expected. 
all parent-child linkages are now gone.  These then need to be rebuilt.
> 
> I can minimize loss by pressing ctrl-s after making changes to the code,
then responding "No" when the first error message appears.  When
following this route, the parent-child links sometimes disappears.
> 
> When all required coding has been done, I close the datamodule, re-open it
and then rebuild the parent-child links.
> 
> Surely the above is not normal, I have not encountered it with previous
versions of dBase.  Has anyone else had a similar experience, and how does one
prevent this from happening?


Pieter,

Can you post a datamodule which uses the DBASESAMPLES tables and then 
give us the steps we need to follow to duplicate the error? Perhaps you 
have found a bug that needs to be reported.

-- 
Geoff Wass [dBVIPS]
Montréal, Québec, Canada

.|.|.|        dBASE info at http://geocities.com/geoff_wass       |.|.|.
.|.|.| ---------------------------------------------------------- |.|.|.