Moving an Access db [modified]
-
We have a small IIS web server that has an ASP (yes, gasp, it's nasty) website that uses as it's data source an access database (please stop laughing). It's an old machine and I'm trying to transfer the whole site to a newer machine that we just got. For the new machine, do I need to install MS Office to be able to read/write to the access db? The old machine has Office 2000, but *not* the Access component of Office. So I'm wondering if I need to even bother installing Office, or if it's needed because of the ODBC drivers? //edit PS: Thanks to everyone for being so helpful on this!
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! Personal 3D projects Just Say No to Web 2 Point Blow
modified on Friday, July 23, 2010 1:43 PM
I think the SQL upgrade wizard thing should be helpful. If not, I wrote a tool called SchemaMaster that can copy the tables and data to MSSQL, MySQL, Excel, dBase, FoxPro, (PostGres and Oracle though not as well tested)... At the same time! LOL... I find Access isn't so evil - but for a web app - it's underpowered for sure. I think Access is actually pretty sweet... one of Microsoft's cool ones in my book. However, trying to upgrade all those forms and not always cooperative queries and things.. not to mention the vba code you might have is where things get dicey. I'd recommend Microsoft's SQL Server or MySQL as your next DB for that thing... MS SQL is the obvious choice if you're in a Microsoft "Shop" and IIS and ASP or .Net is the direction you need to go.
Know way too many languages... master of none!
-
My sympathy man. I did inherit similar web app. Decided to upgrade to SQL server. run migration tool, copied queries to SP and with little effort it was up and running. Access is simply evil. p.s. Got nothing to add to previous suggestions. I'd start right there and Good Luck
Yusuf May I help you?
Simpler is sometimes better. SQLExpress is a big slow cumbersome beast that requires additional runtimes and background services. ASP and an Access database can be used on any Windows machine with nothing more than PWS, IIS, or Babyweb Server. ASP Classic still has a huge following and has a (mostly) pretty logical syntax. I presonally quite like it. More powerful than Access, less hassle than ASP.NET. Just IMHO, if you only require your web app to read/write an Access database, then why not?
-
We have a small IIS web server that has an ASP (yes, gasp, it's nasty) website that uses as it's data source an access database (please stop laughing). It's an old machine and I'm trying to transfer the whole site to a newer machine that we just got. For the new machine, do I need to install MS Office to be able to read/write to the access db? The old machine has Office 2000, but *not* the Access component of Office. So I'm wondering if I need to even bother installing Office, or if it's needed because of the ODBC drivers? //edit PS: Thanks to everyone for being so helpful on this!
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! Personal 3D projects Just Say No to Web 2 Point Blow
modified on Friday, July 23, 2010 1:43 PM
A main reason to install office with Access is you will eventually need to open the database and modify the tables. With Access you will also need to run the compression tool because Access databases don't self compress and can become quite large with lots of activity. With multiple users acessing the database the data can become corrupted at times and being able to open the database, use the compression tool, etc is essential. Make it easy on yourself and install Access!
-
We have a small IIS web server that has an ASP (yes, gasp, it's nasty) website that uses as it's data source an access database (please stop laughing). It's an old machine and I'm trying to transfer the whole site to a newer machine that we just got. For the new machine, do I need to install MS Office to be able to read/write to the access db? The old machine has Office 2000, but *not* the Access component of Office. So I'm wondering if I need to even bother installing Office, or if it's needed because of the ODBC drivers? //edit PS: Thanks to everyone for being so helpful on this!
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! Personal 3D projects Just Say No to Web 2 Point Blow
modified on Friday, July 23, 2010 1:43 PM
please read this before you give up. http://support.microsoft.com/?id=309051
RS
-
We have a small IIS web server that has an ASP (yes, gasp, it's nasty) website that uses as it's data source an access database (please stop laughing). It's an old machine and I'm trying to transfer the whole site to a newer machine that we just got. For the new machine, do I need to install MS Office to be able to read/write to the access db? The old machine has Office 2000, but *not* the Access component of Office. So I'm wondering if I need to even bother installing Office, or if it's needed because of the ODBC drivers? //edit PS: Thanks to everyone for being so helpful on this!
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! Personal 3D projects Just Say No to Web 2 Point Blow
modified on Friday, July 23, 2010 1:43 PM
or please read this if you are using iis7. http://blogs.iis.net/bills/archive/2007/05/21/tips-for-classic-asp-developers-on-iis7.aspx
RS
-
My sympathy man. I did inherit similar web app. Decided to upgrade to SQL server. run migration tool, copied queries to SP and with little effort it was up and running. Access is simply evil. p.s. Got nothing to add to previous suggestions. I'd start right there and Good Luck
Yusuf May I help you?
I agree with you...Access and web applications have never mixed well for me, we always seemed to have major issues with permissions (access has to create a lock file everytime it is opened) and corruption due to concurrent users. Any version of SQL Express (or even MSDE) would be a huge improvement. I would go for the 2008 and use mgmt. studio to upsize. Use OLEDB instead of ODBC for connecting...much faster. Most of the queries that work in Access, should work against SQL Server. Change your date delimiters and concatenation symbols and you've got most of the conversion done.