Print without save

[Michael Humby]

Hi All,

I am busy converting an old application developed in Alpha V1, I'm converting it to V4.5 Runtime for a client.

The app has a form containing about 50 fields and 2 embedded child browses. The form is constantly used for entering data and then printing, works fine.

V1 will allow the user to make temporary changes to field values on the form and then print the form with those changes. Then by default have the option to save or lose the temporary changes.

V4.5 does not allow this because the changes are comitted as soon as another field or object is selected.

Can anyone suggest a way to achieve this because my client finds it very useful
.
i.e. Find a record, view the form, change the value in any number of fields (there can be many), print the form and then have the option to save or lose the changes.

Any tips appreciated

Michael

[Stan Mathews]

RE: Print without save

Michael,

First thought is to design the form with no table fields visible, just store the field values to variables or calculated fields and display these.

The code for the oninit of the form would capture the first set of values. I suppose you would have to have onkey scripts for page up and page down down and any other navigation keys to
1. ask whether to save the current values back to the table
2. move through the table and reset the variables and refresh the display.

[JohnZaleski]

RE: Print without save

I assume you are editing parent field values not the child records. You could make a duplicate record structure of the parent ( omit field rules etc. ). Make a set ( only used for one shot printing ) exactly as your regular set with the dupe as the parent. Copy the report from the original set to the new set. When printing, in xbasic take all object values and add a record to the dupe table. Store the recno() in a variable after adding. Print the report from the dupe set filtering on the recno() that you saved. Not absolutely necessary, but you'd probably want to zap the dupe table occasionally.

[Michael Humby]

RE: Print without save

Thanks Stan and John,

I was hoping there would be a short simple solution since V1 operated this way by default.

I think my first approach for the changes will have to be 'copy the current record'. I shall also start working on the changes using your suggestions but I'm not looking forward to the extra work involved.

Michael

[Tom Cone Jr]

RE: Print without save

Michael,

Here's another idea.

After the user fetches the desired record require him to push a button to begin edits. The button script could store all field values to memory variables. Require the user to push another button to save or to cancel. If he saves, nothing else needs be done. If he cancels, just change the field values back (using values stored in the the memory variables), before saving the record.

-- tom

[Robert Emery]

RE: Print without save

I would create an identical form replacing the fields with variables. In the forms OnInit event, set the variable values equal to corresponding field values.

The variables can be altered to your hearts content without affecting the original record. You could include a button that would save the changes also.

Changing variables values doesn't even require F9 to save changes. You don't enter change mode.

-Bob

[Michael Humby]

RE: Print without save

Thanks All

Wishful thinking. I was hoping someone might offer a simple solution such as 'Activate a specific check box in the form's properties' or something like that. The form has about 50 fields any of which can be changed so I don't fancy the duplicate variable route.

I shall be spending the weekend looking at the record_data_get(), record_data_set() and record_clone() methods. Reading up on the manual this should lead me the required results. Aaagh! Gulp!

Michael

[JohnZaleski]

RE: Print without save

What I don't particularly like about the variable method is that if you display and use variables for data entry rather than field objects, this will negate any field rules. It's not that you can't do it, but it seems like much more work than necessary to accomplish nothing but the printing of an unsaved record.
I think there will be a little work using Tom's suggestion or my suggestion, but not the kind of work necessary to enter everything into variables first and later into the actual field values.

[Robert Emery]

RE: Print without save

I agree, for this application it's probably not the most sensible approach. I use forms like this for Test Data Sheets with Pass/Fail buttons down a column. Some buttons ask for data readings as well. It's info that would be really useless after the fact, other than the required paper-trail, so it never gets saved.

-Bob

[Michael Humby]

RE: Print without save

Hi All,

I have found a solution to make changes to a form, print the form with the changes and then allow the option to keep or lose the changes.

Quite simple because it is mainly from the manual, though it will require more work to operate on embedded browse child values.

'This script is on the form's on fetch and init events to capture the original values.

t=table.current()
Dim shared blob as B
blob=t.record_data_get()


'This script is on the exit button or elsewhere

response=ui_msg_box("","Put old values back?",3)
If response =6 then
choice="Yes"
elseif response=7 then
choice="No"
else
choice="Cancel"
End If

If choice="yes"
dim shared blob as b
t=table.current()
mode=t.mode_get()
If mode=0 'Form is view mode
t.change_begin()
t.record_data_set(blob)
t.change_end(.t.)
ELSE ' Form is already in change
t.record_data_set(blob)
parent.commit()
end if
parent.resynch()
End if

Michael