Hi,
This is a rhetorical question, because I KNOW you've experienced it, but I'd like have a list of people - in order for me not to go mad.
Scenario:
You produce something in MS Access, be it from scratch or an addition to a large project.
You run the app. - it works fine.
You close the developer down - you open it - it runs fine.
You open it the next day - it runs fine.
AND/OR:
You open it the next day - it DOES NOT run fine, it throws errors left, right and centre.
The above scenarios are WITHOUT CHANGES to the app. in the interim. (ABSOLUTELY NO changes - without doubt).
Taking all possibilities into account, and from an high-level computing educational point-of-view: THIS IS NOT POSSIBLE!!!!!!!!!
From any LOGICAL point-of-view: THIS IS NOT possible.
I suggest that Microsoft have some code within Microsoft Access that does it's own little bit of processing at some point or other that changes 'something or other', at different times dependant on 'something or other'.
Can anyone else confirm that the above sounds reasonable to them? Is it just me? Are the MS Access 'quirks' (that appear at will and willy nilly, and under different circumstances really MY problem?).
I am talking about both minor and major problems that evade any single solution, i.e. the type that Microsoft advise to re-write the entire 18 month application as a 'work-around'.
Please comment on this - either way.
Give it to me straight - should I voluntarily sign into a mental institution?
Kind regards,
Darrylle
Never argue with an idiot, he'll bring you down to his level - then beat you with experience. darrylles@hotmail.com
This is a rhetorical question, because I KNOW you've experienced it, but I'd like have a list of people - in order for me not to go mad.
Scenario:
You produce something in MS Access, be it from scratch or an addition to a large project.
You run the app. - it works fine.
You close the developer down - you open it - it runs fine.
You open it the next day - it runs fine.
AND/OR:
You open it the next day - it DOES NOT run fine, it throws errors left, right and centre.
The above scenarios are WITHOUT CHANGES to the app. in the interim. (ABSOLUTELY NO changes - without doubt).
Taking all possibilities into account, and from an high-level computing educational point-of-view: THIS IS NOT POSSIBLE!!!!!!!!!
From any LOGICAL point-of-view: THIS IS NOT possible.
I suggest that Microsoft have some code within Microsoft Access that does it's own little bit of processing at some point or other that changes 'something or other', at different times dependant on 'something or other'.
Can anyone else confirm that the above sounds reasonable to them? Is it just me? Are the MS Access 'quirks' (that appear at will and willy nilly, and under different circumstances really MY problem?).
I am talking about both minor and major problems that evade any single solution, i.e. the type that Microsoft advise to re-write the entire 18 month application as a 'work-around'.
Please comment on this - either way.
Give it to me straight - should I voluntarily sign into a mental institution?
Kind regards,
Darrylle
Never argue with an idiot, he'll bring you down to his level - then beat you with experience. darrylles@hotmail.com