Form Modified Date changes when the orderby property is changed

Form Modified Date changes when the orderby property is changed

Post by Barry Kapl » Thu, 02 Oct 2003 03:34:07


If a used selects to find a recorded in a form by Name or
SSN order then I set the orderby property to the desired
selection. Last, first, middle vs SSN. When the form is
closed, the form modified date changes. This is running
on a network and Access 97 sees that there are changes and
asked if it is ok to save the form. Not to good.

Any Ideas
 
 
 

Form Modified Date changes when the orderby property is changed

Post by Allen Brow » Thu, 02 Oct 2003 14:42:12

You could provide a button on the form that closes it without saving design
changes:
Private Sub cmdClose_Click()
'Save record changes.
If Me.Dirty Then
Me.Dirty = False
End If
'Close without saving design changes.
DoCmd.Close acForm, Me.Name, acSaveNo
End Sub

The real solution, though is going to be to split the database so that each
user has their own copy of the front end, and you avoid the concurrency
issues. There is a database splitter in Access. More info:
http://www.yqcomputer.com/

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://www.yqcomputer.com/

 
 
 

Form Modified Date changes when the orderby property is changed

Post by Barry Kapl » Fri, 03 Oct 2003 02:41:38


Thanks for the tip

I had planned to split the DB for this customer. They
built it. It was 43meg yesterday. Compacted it to 28meg.
I changed the code to supply a recordsource query with a
sort by and dropped the orderby setup. This change didn't
cause a form modified to occur.

I will also use acSaveNo clause on the form close

without saving design
database so that each
the concurrency


or
and