psemianonymous
Programmer
First off, I'm running Access 97 on Windows 2000 SP4.
I'm testing my application right now, and certain behavior (auto-ALLCAPS on one field) that I'm ABSOLUTELY CERTAIN I programmed in is not happening.
I'm absolutely certain that I have made this change. It was about a month ago.
But now it's not there--gone.
I have been working with the same copy of the database for as long as I've had this project. I've never had to restore from a backup (though I do backups on an hourly basis, also guaranteed every day I'm here). So any changes I've made SHOULD be saved. But they're not being saved.
A few things:
1. I do make changes while in DEBUG mode. I know this can be tricky, but I make sure and <CTRL>-S to save the form changes before starting the debugging up again. And then usually, I'll close the form, re-open the form in design mode and verify that the changes are still there. They always are.
2. I use <CTRL>-S to save the form design changes before closing. Too often in the past I've left the warnings completely off so that it dumps any design changes. Not any more. Now I have set the warnings to completely up, at all times, so I can program to ensure that my users will never see the warning boxes.
I DO, however, have Setwarnings set to False every so often--for example, if my program disables the warnings itself.
My basic question is this: Is there something I'm doing wrong? Is anyone else experiencing this? This is not so important in this case (simple enhancement), but when I do bugfixes and they don't 'stick', I get annoyed. Is anyone else seeing something like this?
The scary thing is that I'm getting USED to the idea that my design changes won't always stick, thus I'm subconsciously testing everything twice. Ridiculous.
Pete
I'm testing my application right now, and certain behavior (auto-ALLCAPS on one field) that I'm ABSOLUTELY CERTAIN I programmed in is not happening.
I'm absolutely certain that I have made this change. It was about a month ago.
But now it's not there--gone.
I have been working with the same copy of the database for as long as I've had this project. I've never had to restore from a backup (though I do backups on an hourly basis, also guaranteed every day I'm here). So any changes I've made SHOULD be saved. But they're not being saved.
A few things:
1. I do make changes while in DEBUG mode. I know this can be tricky, but I make sure and <CTRL>-S to save the form changes before starting the debugging up again. And then usually, I'll close the form, re-open the form in design mode and verify that the changes are still there. They always are.
2. I use <CTRL>-S to save the form design changes before closing. Too often in the past I've left the warnings completely off so that it dumps any design changes. Not any more. Now I have set the warnings to completely up, at all times, so I can program to ensure that my users will never see the warning boxes.
I DO, however, have Setwarnings set to False every so often--for example, if my program disables the warnings itself.
My basic question is this: Is there something I'm doing wrong? Is anyone else experiencing this? This is not so important in this case (simple enhancement), but when I do bugfixes and they don't 'stick', I get annoyed. Is anyone else seeing something like this?
The scary thing is that I'm getting USED to the idea that my design changes won't always stick, thus I'm subconsciously testing everything twice. Ridiculous.
Pete
