I have developed a nice database system that controls almost all aspects of one manufacturing department. I am using microsoft Access as the database (Jet?) and I use forms to enter data. The front end is done all in data access pages hosted on an IIS 5.0 server. This allows all of the sales people to look at their orders. Everything works great, the sales people love it and my job is pretty easy. The problem is that our General Manager loves it also. He wants me to make a much more robust version that will keep track of multiple departments and at least three manufacturing departments. Sales people will actually turn in orders through the internet. My question is about the limitations of Access. I will have about 25 users logged into the DB changing data in the tables at any given time. I'm wondering if I should switch to a different database such as MySQL or MS SQL. I would use one box for the SQL database, one box for the IIS 5.0 webserver, and develop pages in ASP for the front end. Access is sooo easy though. Even though DAPs are no longer supported, I could use the VBScripting knowledge I've learned with ASP. Also, I am a one man team except for a guy that designs web pages so that has to weigh in with the development side of things.
I appreciate any advice you may have.
Thanks,
James
I appreciate any advice you may have.
Thanks,
James
Comment