MS Access is NOT and Enterprise Solution
-
There are other options, such as MySQL, that provide enterprise databases that don't break the bank. Bit of a learning curve if its new to you, but worth considering.
It's the answer, write the data layer separately, and in one month when they come burning on fire, move the solution to MySql, i have done heavy applications on mysql, and are still running. In other hand i think that someone with your capabilities and honesty most get into a Business-Software-Man. Think about it!
-
I have found that the second a client finds out what can (potentially) be done with MS Access (or any other cheap solution) they then try to see how much work they can get done with this database software program. This is a bad thing in so many respects and on so many levels. I proposed C# with SQL Server - minimum. They wanted and "they payed" my company to see what I can get done with Access 2007. I told them their dreams will turn into nightmares in less than one month's time. They did not believe me. My advice and concerns have turned into reality. Microsoft Access is not meant to be a multi-user data entry system...it is not dependable and it crashes all the time and is constantly prone to corruption. Even Microsoft says that Access is not meant for this kind of work. I had no choice in the matter. I don't work for myself. I am not independently wealthy. I "need" this job right now; I have a family and bills to pay. Yet I am forced into working in a constant state of futility. Our client is a big-house and pays very well. Why couldn't they pay for the right solution to the problem the first time instead of taking the "usual" cheap man's way out is beyond me. I don't even know why my company allowed this contract to take off in the first place (a side from the money). I am emotionally spent. I need a vacation. They want me and another dumb-ass programmer to do a "complete" re-write. Thanks for reading.
My first job in IT saw the company I worked for using access for all their databases. These databases were accessed over WAN links by upwards of 30 people at a time! Watching all the frustration produced was not entertaining at all. The only reason this was happening is because the IT person making these databases was all they knew and they were very close with the IT director who themselves wasn't even an IT person by profession (a masters in counseling does not equal IT director but somehow in this company, it did). They just didn't know any better. Over a few years time I was able to change their minds and set up a sql 2K system using vb web forms and some win forms but it was a painful transition since the technology wasn't known by the IT director or his right hand girl (the access developer who also wasn't professionally trained in any IT technologies or methodologies in any way (a music degree landed her the IT job?!)). This was another classic situation where the higher ups hate not being in control (they didn't know how to work with the technologies so that made them nervous and suspicious in everything I did for them even though it was my job to do so). Thankfully, I moved on from that crazy place (pun intended).
-
I used access a lot to prototype. If your client is not able to specify his needs and expectations in full (not unusual), Access might be your solution. Just make sure that your client agrees that you will build the final solution with some proper tools. Not too hard to port an access solution to a c#/sqlserver solution. This can be an efficient approach. One of my first employers put it like this: "you have to build your dreamhouse twice.", justifying prototyping.
robbertnix wrote:
I used access a lot to prototype.
I do too as well. However, in this case "prototyping" was not the intention. Porting this to SQL Server is no big deal to me. It's just extra work. This stuff happens all the time in our profession but sometimes it just get to me.
-
Michael Haines wrote:
I totally disagree! MS Access is a much saner choice than some that I have seen.
So you think that MS Access is a viable and good choice for an Enterprise Data Entry system with multiple concurrent users compared to let's say SQL Server or Oracle? Do expand on this because I am truly at a loss as too how this is remotely possible. :confused: I am quite sure you know that Access has nothing in regards to Stored Procs, Triggers, and other nifty little gadgets that are common place in Enterprise database applications. I have never seen Excel used as an Enterprise level database...ever. Now, that is not to say it doesn't happen, I just have never heard of that.
I am not advocating MS Access as the right solution for anything. I am merely pointing out that there are worse choices. By the way, "Enterprise" is a marketing term that can mean a wide variety of things. It does not always mean that stored procedures, triggers, or other gadgets are necessary to provide a viable solution. You are here - through no fault of mine!
-
I have found that the second a client finds out what can (potentially) be done with MS Access (or any other cheap solution) they then try to see how much work they can get done with this database software program. This is a bad thing in so many respects and on so many levels. I proposed C# with SQL Server - minimum. They wanted and "they payed" my company to see what I can get done with Access 2007. I told them their dreams will turn into nightmares in less than one month's time. They did not believe me. My advice and concerns have turned into reality. Microsoft Access is not meant to be a multi-user data entry system...it is not dependable and it crashes all the time and is constantly prone to corruption. Even Microsoft says that Access is not meant for this kind of work. I had no choice in the matter. I don't work for myself. I am not independently wealthy. I "need" this job right now; I have a family and bills to pay. Yet I am forced into working in a constant state of futility. Our client is a big-house and pays very well. Why couldn't they pay for the right solution to the problem the first time instead of taking the "usual" cheap man's way out is beyond me. I don't even know why my company allowed this contract to take off in the first place (a side from the money). I am emotionally spent. I need a vacation. They want me and another dumb-ass programmer to do a "complete" re-write. Thanks for reading.
I realize this isn't the best solution but you may can get away with it and it would at least reduce your pains. I assume if they can even think of MS Access then they must not have but just so many users and so SQL Express which is free to use could serve as a back end to a MS Access front end. Still not the best solution but its fare better then all ACCESS. Another possible alternative is to build the thing using SQL Express as the data store and whatever your favorite programming language is for the front end and then design a simple MS Access DB App that does nothing more than launch your real application giving the appearance as though its MS Access. Why does a company like this that can afford the right process opt instead for something on the cheap that will most likely not work? Because the decision makers are not computer literate and so they see any expenditures on computer technology as a waste and a necessary evil. I use to work in property management (apartment rentals) and in that industry this is a BIG problem with any company that has executives/owners over 40-50 years of age. These folks have no problem dropping $25K for a few dozen bushes around the property but tell them they need to drop $10k on a good server for their DB and they accuse you of trying to steal form them. These folks often are clueless as to the value of technology and theres not much you can do except wait for them to retire or run to business into the ground