Record moves on save

[John Castle]

I have a form based on the set:

vehicle -" jobs -" parts

and when adding a new or modifying an existing job for a vehicle open another form based on another set:

jobs -" fitters
-" parts

When I go to save the record in the jobs form, usually when adding a new job c.f. modifying an existing job, the job record displayed will often move to a previous job done for the same vehicle.

I have turned off record navigation in the job form and the save button does nothing but save the record.

Any ideas?

[Stan Mathews]

RE: Record moves on save

Does the form have built-in ordering?

Form in design mode, Form menu, Properties, Filter/Order tab...

[John Castle]

RE: Record moves on save

The main form based on the vehicles-"jobs and -"parts set is ordered by vehicle registration number.

The jobs form based on the jobs-"fitters and -"parts does not have any order as only one job is open at a time.

[Tom Cone Jr]

RE: Record moves on save

Can you post an example for us to examine?

-- tom

[John Castle]

RE: Record moves on save

Here is a stripped down version.

To logon select administrator and password xmts

Go to the form Jobent and select a vehicle (some already in) then go to the Jobs tab and click on the add new job button above the upper browse. Fill in the job details (a couple of fields are required so use dots etc).

If you do not add any parts to the job, irrespective of how many fitters you have added to work on it, it saves ok without moving to another job.

If however you enter 1 or more parts, it usually moves to another job. Also if you go to the invoice tab on the job ticket and change or type into any fields there, it will move.

I am lost as to why it is doing this.

[Tom Cone Jr]

RE: Record moves on save

John,

I think the trouble lies in your Save button on the called form. The form is based on a set that includes two child tables. Data entry into the children is done using separate embedded browses. Your single SAVE button uses a command that saves the primary table record only.

In Alpha Five data entry occurs one table at a time. There is no such thing as a "set record" which can be saved with a single command. Instead, data entry begins and must be saved, one table at a time. First the primary table, then a child, then the next child.

You can see this yourself if you begin a new job, enter a new Fitter record, but don't press your Save button. Instead, use the F9 key to save the Fitter (child) record. Then move to the parts browse and enter a new record, using F9 to save it there.

the form does not crash, Alpha does not lock up, and the record pointer does not arbitrarily jump to a different job.

I'm uncertain what to advise on the best way to fix this. Certainly one approach would be to use 3 different save buttons, one for each table, hiding and showing the "current" one depending upon which table is being changed. But it seems clear to me that your one button approach using

formname.commit() to save the records in linked 1:N child tables will not suffice.

Hope this helps.

-- tom

[martinwcole]

RE: Record moves on save

Tom and John,

Although rare, I have run into situations like this, too.

Here is a brute force method that will work:

Save Button:
dim rnum as n
rnum=table.current(1).recno() 'the parent record
'invoice is the form name
invoice.commit()
'only fire if it jumped
if table.current(1).recno() "" var-"rnum
Invoice.Recno_goto(rnum)
end if

[John Castle]

RE: Record moves on save

Thanks for the help.

I have put record save buttons above each browse and asked the users to click on them when they exit each and before entering the next field on the form and this works.

Tried using on row change event to save the record in the browse but that locked up the form.

[martinwcole]

RE: Record moves on save

John, where you are using an embedded browse, the record necessarily saves/commits when you change rows or depart the browse - thus the canrowchange and candepart browse events are useful for using code that fires before the browse record saves.

you don't need to commit the browse, in other words.