I'd like to ask this question of all the experienced Access developers...
I have started making an Access 2000 application. I plan to sell it to very small offices in a small niche market. Usually these offices don't have more than 5 computers on a network.
Now I am having second thoughts about embarking on this project, mostly because of all the corruption problems I read about with Access. I have this nightmarish vision of dozens of offices calling and complaining about endless problems. What I am not sure of is if my concerns are valid.
So I'd like to ask you all... is this fear justified? Is Access really that bad, a little bad, or not bad at all? Do you have lots of corruption headaches or other frustrations with your Access apps, or is your life as an Access developer happy and relatively trouble-free?
Thanks for any guidance.
Jack
I have started making an Access 2000 application. I plan to sell it to very small offices in a small niche market. Usually these offices don't have more than 5 computers on a network.
Now I am having second thoughts about embarking on this project, mostly because of all the corruption problems I read about with Access. I have this nightmarish vision of dozens of offices calling and complaining about endless problems. What I am not sure of is if my concerns are valid.
So I'd like to ask you all... is this fear justified? Is Access really that bad, a little bad, or not bad at all? Do you have lots of corruption headaches or other frustrations with your Access apps, or is your life as an Access developer happy and relatively trouble-free?
Thanks for any guidance.
Jack