from Jet to MSDE
-
Okay, so I have this product that modifies a jet database, and now it doesn't work. The program who's database I was modifying switched to MSDE databases. So, I'm assuming that I must do something different programmatically. I just don't know what. Also, I can't even figure out how to create a test MSDE database. I don't even know if it's still a .mdb. Can anyone help? halblonious
-
Okay, so I have this product that modifies a jet database, and now it doesn't work. The program who's database I was modifying switched to MSDE databases. So, I'm assuming that I must do something different programmatically. I just don't know what. Also, I can't even figure out how to create a test MSDE database. I don't even know if it's still a .mdb. Can anyone help? halblonious
-
Okay, so I have this product that modifies a jet database, and now it doesn't work. The program who's database I was modifying switched to MSDE databases. So, I'm assuming that I must do something different programmatically. I just don't know what. Also, I can't even figure out how to create a test MSDE database. I don't even know if it's still a .mdb. Can anyone help? halblonious
Do you have Access? If so, it includes a tool to 'upgrade' your database to SQL Server form. It isn't perfect, but it's a start. In theory, a MSDE database is identical to one made with SQL Server. Try the tool, if you have it, then check the docs on MSDE at MSDN for linking it all together. "Another day done - All targets met; all systems fully operational; all customers satisfied; all staff keen and well motivated; all pigs fed and ready to fly" - Jennie A.
-
Okay, so I have this product that modifies a jet database, and now it doesn't work. The program who's database I was modifying switched to MSDE databases. So, I'm assuming that I must do something different programmatically. I just don't know what. Also, I can't even figure out how to create a test MSDE database. I don't even know if it's still a .mdb. Can anyone help? halblonious
For one, you no longer have MDB files, you have MDF and LDF files. However, these files are not self-contained like the MDBs, so you can't just move them around. It's best to let SQL Server deal with it if you're just starting out. For two, if you're using DAO to connect to Access, I'd recommend switching to ADO if possible. For three, to *easily* manage your database, you'll need a replacement for a tool for a program that comes with the real SQL Server called Enterprise Manager. Here's one such replacement... http://www.webattack.com/get/sqlexecms1.html[^] And lastly, SQL Server comes with many tools that MSDE does not. One in particular is the DTS wizard and editor. You can run a DTS package with MSDE, but not create one (unless you do everything via code that is). The last I heard Microsoft was selling SQL Server Developer Edition for only $49. It's way better to develop your DB with the real deal, and then just bring it over to MSDE when you're done. Jeremy Falcon