Icon View Incident Report

Serious Serious
Reported By: Robert Schiller
Reported On: 11/10/1998
For: Version 1.07 Build 1
# 238 Transaction Commit Forcing Browse Mode and Causing Premature Post

I'm calling Patient Edit from my VisEdit Form. This means I have the Visit table in the Visit Data Module either in Insert or Edit mode. Everything above works ok until I get back into the VisEdit and then I get a Dataset is not in Insert or Edit mode error when attempting to leave devPtId. What's happening
here? I guess I can't leave one table in Insert mode and put another into Insert mode at the same time?

procedure TfmVisEdit.sbPatientClick(Sender: TObject);
begin
NewPatientId := '';
dmPatient := TdmPatient.Create(Self);
dmPatient.taPatient.Insert;
fmPtEdit :=TfmPtEdit.Create(Self);
fmPtEdit.ShowModal;

devPtId.SetFocus;
devPtId.Text := NewPatientId;

fmPtEdit.Free;
dmPatient.Free;
end;

I commented out the transaction stuff in my Patient CommitRecord. For some reason the transaction is what's causing the Visit table to go out of Insert mode.


Comments Comments
Problem was with the transactions causing a Post (CheckBrowseMode) on datasets before a Commit even if the dataset did not participate in the transaction (was not changed).


Resolution Resolution
Fixed Problem on 11/18/1998 in version 1.08 build 1
Image