Ooh, I just had a thought. If there was a way to implement it so that the macro security was set to high and the code not enabled, it should work. I don't know that there would be a way to do that though.
Ooh, I just had a thought. If there was a way to implement it so that the macro security was set to high and the code not enabled, it should work. I don't know that there would be a way to do that though.
Yea, I wish i could change the form, but i can not unfortunately. Trying to find another way around it
I understand the procedure runs but if nothing is changed isn't the bChangedAndNotSaved boolean variable False and the Input Box would not popup? What sets the variable to True?
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
Hmm, the one question we haven't asked is "what is the code that dsk96m is using to pull the data from Excel" and maybe that is the cause for the changes it thinks happened.
I am simply pulling values from cells into an access table.
Yes, something must be setting that variable to true. Provide code and maybe the workbook as well for analysis.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.