|
Thank you to Satcomer and nixgeek for constructive comments.
The other commenteers could learn from these two who obviously have real life experience with the issues and actively work for solutions.
Note please, that we don't write that macs are sh.t, neither that Access is God, neither that Macs and Access can't coexist, just that some (few) know how to handle this combo - pros like Satcomer and nixgeek - and some (most) - lack this knowledge or refrain from obtaining it.
The advice we give is for the situation where the Mac people are ignorant - the typical attitude is that "if this Windows/Access/Evil Empire crap doesn't work in our Mac environment as is, it is .. crap. Those win geeks are not coming telling us to do anything". All Mac people are friendly, you say, but then read the comments here again. Time has learned me that this discussion is not worth five minutes and, in that case, you just have to take your own precautions like those described.
Note too, that we don't claim that Access/JET is the answer to anything. It is a file based database which is extremely good for what it is designed for. It is not comparable with server based database engines.
Finally, Access/JET does run mission critical applications around the world wether you like it or not - and at just about zero cost. We have clients here running different applications with Access/JET as the backend database experiencing 0 (zero) failures for more than 10 years. This is a fact.
Still, from case to case, we may very well advice clients to use some other database for their specific task if we can see Access/JET won't fit the bill.
/gustav
 |