Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MS Conspiracy theory

Status
Not open for further replies.

Darrylles

Programmer
Feb 7, 2002
1,758
GB
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
 
Hi Darrylle
You are right and then again you are not :)

The database container (where all tables ques, forms, code, etc. is stored) some times goes souer during the development, of the database/program, I am not shure why, sry, but when this happens to me - the program behaves erratic - I create a new empty container and import all elements into this new container and ....... problem solved. Dont forget to check your refrences :-D


Herman

They say that crime doesn't pay... does that mean my job is a crime?
 
Darrylle,

After years of working with many different progrmming tools, most from Microsoft, I can say I agree with you that a perfectly function app can just go sour. The same thing can happen to a PC and it's operating system.

But, I do not think it is a 'Conspiracy', more it is just a sign of the times.

On any given PC there might be 20 or 30 thousand files. Who knows how many are loaded by the operating system just at boot up. Are they always loaded in the same sequence? I think not! If a Printer driver, from a vendor fails, then the spooler from Microsoft fails, then the apps print routine fails, well who is to blame if all that was wrong was the printer cable was partially disconnected.

Now, add all the auto updates that occur. Most PCs running Norton Anti Virus (for example) will go out and check for virus and program updates and modify your PC everyday. Many Spyware type apps install and update behind the scenes(daily). In a nutshell, any system that is connected to the internet almost never boots with the same drivers every day. There is always something that is getiing changed, so..

I guess the most important thing is to make backups of your work often..... or go back to windows 98, and remove any internet or network connections and then you might have a static development environment.

I share your frustrations, but it is a sign of the times..

Hap [2thumbsup]


Access Developer [pc] Access based Add-on Solutions
Access Consultants forum
 
Personally, I think it's a bunch of little gnomes running around inside my computer with tiny magnets rearranging my hard drive while I'm at home sleeping... but hey, it could be a sign of the times ;-)

I agree that it is _extremely_ frustrating, and that MS products seem to do it a bit more than others. I guess it's the price we pay for letting MS take over the PC market. Not that there's anything we can do about that now, but at least there are workarounds. I've had to do what Herman said (import all to a new db) to fix problems. Why that works... who knows. But it is better than rewriting!
 
I've been programming in Access with VB for over five years and I too have experienced problems that absolutely have no explanation. Sometimes a control on a form that has worked forever quits acting like it should and you just have to delete the control and put another there. Also, at least three times in the last couple years I've had to import all db ojbects into a new db container from a db that was working OK, but for some reason one day wouldn't load anything - giving lots of ugly errors. But, many times I've marveled that things work as well as they do as often as they do.

Good luck. AND ALWAYS BACK UP YOUR CODE!!!!
 

I've also had a similar sounding problem, but with a twist. Upon opening the Access DB, I click on the Modules tab, I then click on the Class Icon looking button that opens the code window. But sometimes one click is not enough. If I have to click twice I know I'm in trouble. The code window opens but looks subtly different. There are no lines between procedures and my Project Explorer and Properties that are usually docked on the right side are missing. From experience I know that the db is hosed, but here is the weird part, if I add a new form, throw on some controls, save the new form, exit out of the application and open the db again it will be okay. Does this sound familiar to anyone?

Thanks,

-- Joe --
 
I've had some episodes where I couldn't open a form without causing an Access Violation 0x00000...005, and running /decompile instantly (and permanently) solved the problem.

Weird code-related errors can be solved using /decompile - then recompiling the code.


PS--Tony Toews has apparently removed the awful 'granite' background image from his Access tips site, huzzah! No more "ugly but useful" disclaimers--now I can just say "His site is excellent," without saying "...but 1997-era web page ugly.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top