M
Michael
I have just spent several early morning hours chasing some bizarre form
behaviour.
I have a form (Access 2003) which normally opens with OpenArgs, requires
entry at a few controls and updates a record (or creates) as it closes.
(It is always executed from elsewhere in operation).
I decided to add a control (bound) to a record column/field called DT, which
happens to be a string version of a Date Time, but is just text.
So logically - and automatically, the control was also called DT. AS soon as
I completed adding the Control - DT, the mdb created the automatic Backup
version and the request to send the message to Microsoft came up and the mdb
closed down.
When I reopend the mdb, I could no longer open the form in either design or
run mode.
If I tried exporting it, or creating a new mdb and importing it, I got some
message about it not having an index. The form was lost from any usage.
Fortunately the code behnd the form was obtainable via Macro / Code.
After several attempts and repeats of the above, in desperation, I called
the control XYZ- still attached to field DT and IT NOW WORKS PERFECTLY and
as expected.
Has anybody else had this behaviour with a control called DT - or similar?
TIA
Michael
behaviour.
I have a form (Access 2003) which normally opens with OpenArgs, requires
entry at a few controls and updates a record (or creates) as it closes.
(It is always executed from elsewhere in operation).
I decided to add a control (bound) to a record column/field called DT, which
happens to be a string version of a Date Time, but is just text.
So logically - and automatically, the control was also called DT. AS soon as
I completed adding the Control - DT, the mdb created the automatic Backup
version and the request to send the message to Microsoft came up and the mdb
closed down.
When I reopend the mdb, I could no longer open the form in either design or
run mode.
If I tried exporting it, or creating a new mdb and importing it, I got some
message about it not having an index. The form was lost from any usage.
Fortunately the code behnd the form was obtainable via Macro / Code.
After several attempts and repeats of the above, in desperation, I called
the control XYZ- still attached to field DT and IT NOW WORKS PERFECTLY and
as expected.
Has anybody else had this behaviour with a control called DT - or similar?
TIA
Michael