G'day to my fellow beta testers, At 17:52 17/11/02 +1100, you wrote:
You will also be very PLEASED to know that since the first beta of in-line patch-3 (over 8 months ago), all CURRENT and ACTIVE R:BASE Developers, Users and Corporate Clients have been using/testing their MISSION_CRITICAL applications.
Here is why I would advise against using beta software
on production databases.
If you use the following technique could I please ask
you to test it (on a backup copy of your database) to
see if it just me or my database?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In many places in BizMan I have a form with a tiered
region to display all records of a type with a button
on the form to go to a specific record to make any
edits for that row.
Sometimes the called form is a non-editable one to
display the full data for a transaction without the
user being able to edit it. This will have a button
on it to enable the user to bring up a third form in
EDIT mode.
Last week I noticed that I was unable to save changes
made to a record after going from the record in a
tiered region to another form that displayed only that
record.
What appears to be happening is that the changes made to the columns in
the lower form are being saved down to the table but when the lower form
is closed (and without making any changes to the record in form 1) the
data in the first form overwrites the changes made in the lower form.
This used to happen only if changes were made to the data on the first
form after coming back to the first form from the second but now the
first form is saving the data displayed in the first form whether or not
any changes have been made to the data.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I have just done some more work on this and can advise the following.
I have a form that displays a list of bills in a region.
At the top of the form is a [View] button which displays
a two table form in which to view the entire bill record.
On the View form there is an [Edit] button which displays
a copy of the [View] form with the data editable.
R:BASE crashed half way through entering a new bill record
so I needed to go in and enter the detail section and update
the header for the bill.
I went to the list form and clicked on the [View] button,
then clicked on the [Edit] button on the view form,
made the changes in the edit form,
exited to the view form,
pressed [F8] to refresh the data and observed that the record
had, in fact, been saved with the amended data,
but when I went back to the list form the header data had
reverted to the pre-edit version.
The list form is overwriting changes made to the data in the
lower forms.
I then tried adding the [Edit] button to the list form so
I was removing a step in the process but the changes were
still overwritten on returning to the list form.
I then exited R:BASE and removed the latest beta files from
the folder and reverted to a backup (version 6.5++1.851xRT03).
I then tried to perform the edit with the same disastrous
results. So somehow a change has been made to the database
so that despite reverting back to an earlier version of R:BASE
in which this procedure worked, it no longer works.
This has, unfortunately, left my production database is an
unusable condition and I am hopeful that:
1. The problem can be replicated and
2. RBTI can fix it.
Hence the heads up.
Warmest regards,
Tom Grimshaw
coy: Just For You Software
tel: 612 9552 3311
fax: 612 9566 2164
mobile: 0414 675 903
post: PO Box 470 Glebe NSW 2037 Australia
street: 3/66 Wentworth Park Rd Glebe NSW 2037
email: [EMAIL PROTECTED]
web: www.just4usoftware.com.au
"... the control of impulse -- is the first principle of civilization."-- Will Durant,
Pulitzer Prize winning philosopher, writer and historian
the most needed product in the world can be found at
www.thewaytohappiness.org
This email and any files transmitted with it are confidential to the intended recipient and may be privileged. If you have received this email inadvertently or you are not the intended recipient, you may not disseminate, distribute, copy or in any way rely on it. Further, you should notify the sender immediately and delete the email from your computer. Whilst we have taken precautions to alert us to the presence of computer viruses, we cannot guarantee that this email and any files transmitted with it are free from such viruses.
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/
