I am not a experienced user of Access World and I did not know where else to put this post than in a new thread.
I know this is a harsh post but I simply needed to vent my frustrations.
25 years ago I gave up on using Access for anything else than the most simple tasks. It was simply too troublesome to work with, mostly because of unrepairable broken databases.
Then 6 month ago I thought I would give it another try. Now 6 month later I am this close (0.0000….. mm) to give up on Access again.
I am working on a project where I have a utility database MyUtils.accdb referenced by an application database SomeApp.accdb. This morning I decided to rename MyUtils.accdb to Utils.accdb and did the following:
I’ve had great problems using ActiveX components like Windows Media Player, TreeView, ListView and VLC media player all of which works smoothly when I test them in a C#-application on the .NET-platform. As far as I remember this is the 6’th time in 6 month I am left with an unrepairable database.
The only thing that hasn’t caused me any problems, is the data part of my application but perhaps that is due to the fact that I’m using SQL Server as the underlying database.
Okay. Perhaps I should have been warned because the first thing you see on Access’ info page is a big fat button with the caption Compact & Repair Database.
I have only once in my 35 years as a software developer used a tool this bad and that was 25 years ago when I used Access for the first time. I would be ashamed of myself if had released a piece of software as buggy as Access.
One of the members in here, I don’t remember who, has written something like this in his signature: After 20 years working with Access I do not have much hair left to give. I know what he means.
How do you guys keep the flag flying?
I know this is a harsh post but I simply needed to vent my frustrations.
25 years ago I gave up on using Access for anything else than the most simple tasks. It was simply too troublesome to work with, mostly because of unrepairable broken databases.
Then 6 month ago I thought I would give it another try. Now 6 month later I am this close (0.0000….. mm) to give up on Access again.
I am working on a project where I have a utility database MyUtils.accdb referenced by an application database SomeApp.accdb. This morning I decided to rename MyUtils.accdb to Utils.accdb and did the following:
- I closed both databases.
- I opened SomeApp and removed the reference to MyUtils.accdb and closed SomeApp again.
- I renamed MyUtils.accdb to Utils.accdb
- I opened SomeApp and created a reference to Utils.accdb
I’ve had great problems using ActiveX components like Windows Media Player, TreeView, ListView and VLC media player all of which works smoothly when I test them in a C#-application on the .NET-platform. As far as I remember this is the 6’th time in 6 month I am left with an unrepairable database.
The only thing that hasn’t caused me any problems, is the data part of my application but perhaps that is due to the fact that I’m using SQL Server as the underlying database.
Okay. Perhaps I should have been warned because the first thing you see on Access’ info page is a big fat button with the caption Compact & Repair Database.
I have only once in my 35 years as a software developer used a tool this bad and that was 25 years ago when I used Access for the first time. I would be ashamed of myself if had released a piece of software as buggy as Access.
One of the members in here, I don’t remember who, has written something like this in his signature: After 20 years working with Access I do not have much hair left to give. I know what he means.
How do you guys keep the flag flying?