If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Sub-Form Properties Changed...
I have a data entry form with a sub-form. Somehow on ocassions, which I
can't track, the sub-form properties: Allow Edits, Alllow Deletions and Allow Additions, gets changed. I've been trying to observe users and their habits for the past few months, in the hope of trying to figure out the reason for these changes. Somehow I can't figure out what would cause these changes. There is nothing in the form coding that even addresses these properites. Is there someone out there who can explain this so that I can fix this problem for good? Right now, I have to go and change the properties manually everytime this happends. Thanks, Fred |
#2
|
|||
|
|||
Sub-Form Properties Changed...
I'm pretty sure a SubForm inherits these settings from the MainForm. Does
that help at all? Fred wrote: I have a data entry form with a sub-form. Somehow on ocassions, which I can't track, the sub-form properties: Allow Edits, Alllow Deletions and Allow Additions, gets changed. I've been trying to observe users and their habits for the past few months, in the hope of trying to figure out the reason for these changes. Somehow I can't figure out what would cause these changes. There is nothing in the form coding that even addresses these properites. Is there someone out there who can explain this so that I can fix this problem for good? Right now, I have to go and change the properties manually everytime this happends. Thanks, Fred -- RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro Please post back to this forum so all may benefit. Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/201001/1 |
#3
|
|||
|
|||
Sub-Form Properties Changed...
The Subform's orginal property always changes after a few weeks of usage.
Even if it the Subform inherits the MainForm's property, what would change the property of the Subform? Why wouldn't the Subform's property change immediately? "ruralguy via AccessMonster.com" wrote: I'm pretty sure a SubForm inherits these settings from the MainForm. Does that help at all? Fred wrote: I have a data entry form with a sub-form. Somehow on ocassions, which I can't track, the sub-form properties: Allow Edits, Alllow Deletions and Allow Additions, gets changed. I've been trying to observe users and their habits for the past few months, in the hope of trying to figure out the reason for these changes. Somehow I can't figure out what would cause these changes. There is nothing in the form coding that even addresses these properites. Is there someone out there who can explain this so that I can fix this problem for good? Right now, I have to go and change the properties manually everytime this happends. Thanks, Fred -- RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro Please post back to this forum so all may benefit. Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/201001/1 . |
#4
|
|||
|
|||
Sub-Form Properties Changed...
Do you use DoCmd.Close acForm, Me.Name, acYes anywhere?
Fred wrote: The Subform's orginal property always changes after a few weeks of usage. Even if it the Subform inherits the MainForm's property, what would change the property of the Subform? Why wouldn't the Subform's property change immediately? I'm pretty sure a SubForm inherits these settings from the MainForm. Does that help at all? [quoted text clipped - 11 lines] Thanks, Fred -- RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro Please post back to this forum so all may benefit. Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/201001/1 |
#5
|
|||
|
|||
Sub-Form Properties Changed...
Yes I use those in the Main Form only...not the subform with the problem...
"ruralguy via AccessMonster.com" wrote: Do you use DoCmd.Close acForm, Me.Name, acYes anywhere? Fred wrote: The Subform's orginal property always changes after a few weeks of usage. Even if it the Subform inherits the MainForm's property, what would change the property of the Subform? Why wouldn't the Subform's property change immediately? I'm pretty sure a SubForm inherits these settings from the MainForm. Does that help at all? [quoted text clipped - 11 lines] Thanks, Fred -- RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro Please post back to this forum so all may benefit. Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/201001/1 . |
#6
|
|||
|
|||
Sub-Form Properties Changed...
Are you aware that the acYes at the end is for saving changes to the *form*
and not for saving the current record? It should really be: DoCmd.Close acForm, Me.Name, acSaveNo Fred wrote: Yes I use those in the Main Form only...not the subform with the problem... Do you use DoCmd.Close acForm, Me.Name, acYes anywhere? [quoted text clipped - 8 lines] Thanks, Fred -- RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro Please post back to this forum so all may benefit. Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/201002/1 |
#7
|
|||
|
|||
Sub-Form Properties Changed...
I don't use acYes.
"ruralguy via AccessMonster.com" wrote: Are you aware that the acYes at the end is for saving changes to the *form* and not for saving the current record? It should really be: DoCmd.Close acForm, Me.Name, acSaveNo Fred wrote: Yes I use those in the Main Form only...not the subform with the problem... Do you use DoCmd.Close acForm, Me.Name, acYes anywhere? [quoted text clipped - 8 lines] Thanks, Fred -- RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro Please post back to this forum so all may benefit. Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/201002/1 . |
#8
|
|||
|
|||
Sub-Form Properties Changed...
I miss typed the string. It should have been acSaveYes instead of acYes. The
point I was trying to make is there are ways for the properties to be changed of which you may not be aware. Properties do not change by themselves. Fred wrote: I don't use acYes. Are you aware that the acYes at the end is for saving changes to the *form* and not for saving the current record? It should really be: DoCmd.Close [quoted text clipped - 7 lines] Thanks, Fred -- RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro Please post back to this forum so all may benefit. Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/201002/1 |
#9
|
|||
|
|||
Sub-Form Properties Changed...
For this particular form, I just close the form by "DoCmd.Close" only. This
is done with the "close" command button. Two other ways of closing the form is; by "clicking" on the X (close window) and/or by any abnormal exit (power down, task manager...etc). I was not aware that the DoCmd.Close acForm, Me.Name, acSaveNo can change the form property. If it does, why does this (property change) not occur constantly. It occurs very intermittently (once in a blue moon), and to think this application is used by an average of 3 users a day. I've given up trying to figure this one out. This application has been successfully running for more than 5 years now. This is the only problem that I"ve been encountering these past 2 years (when it started). I appreciate your patience and help. Let me know what to do...please === "ruralguy via AccessMonster.com" wrote: I miss typed the string. It should have been acSaveYes instead of acYes. The point I was trying to make is there are ways for the properties to be changed of which you may not be aware. Properties do not change by themselves. Fred wrote: I don't use acYes. Are you aware that the acYes at the end is for saving changes to the *form* and not for saving the current record? It should really be: DoCmd.Close [quoted text clipped - 7 lines] Thanks, Fred -- RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro Please post back to this forum so all may benefit. Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/201002/1 . |
#10
|
|||
|
|||
Sub-Form Properties Changed...
All I can suggest is putting some diagnostic coede in the Unload event that
writes the current value of the properties to a text file along with a time stamp and any other information you might fine useful. It may help you pin it down. I guarantee you what you are describing is not normal operation and may point to other issues with the system even though as you say it has been running for 5 years. OS's are being patched and changed as are applications such as Access. I would treat it like a nagging loose end. Fred wrote: For this particular form, I just close the form by "DoCmd.Close" only. This is done with the "close" command button. Two other ways of closing the form is; by "clicking" on the X (close window) and/or by any abnormal exit (power down, task manager...etc). I was not aware that the DoCmd.Close acForm, Me.Name, acSaveNo can change the form property. If it does, why does this (property change) not occur constantly. It occurs very intermittently (once in a blue moon), and to think this application is used by an average of 3 users a day. I've given up trying to figure this one out. This application has been successfully running for more than 5 years now. This is the only problem that I"ve been encountering these past 2 years (when it started). I appreciate your patience and help. Let me know what to do...please === I miss typed the string. It should have been acSaveYes instead of acYes. The point I was trying to make is there are ways for the properties to be changed [quoted text clipped - 7 lines] Thanks, Fred -- RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro Please post back to this forum so all may benefit. Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/201002/1 |
|
Thread Tools | |
Display Modes | |
|
|