Just another case of forcing net on developers ?
-
SQL Server may be overkill but MSDE is not. It's based of the SQL Server engine but it is meant to replace Access/Jet. It's been around since SQL Server 7.0. It uses SQLOLEDB and is 100% compatible with SQL Server. Access is a horrible piece of crap. I know, I've worked with it extensively in the past so I don't have a probably with seeing support for it go. Jason Gerard
-
Hi all, I just read the following article on MSDN http://www.msdn.microsoft.com/library/default.asp?url=/library/en-us/Dnmdac/html/data\_mdacroadmap.asp?frame=true I really feel :mad: :mad: :mad: about that. Its just 1 year since I moved an VC++ app from DAO to ADO using the Access OLE DB provider. Guess what, its all legacy know with no foreseeable future. So in the MS "vision" and data access strategie I have to move to MC++ and use ADO.NET and also have to move to SQL Server. Bud that's absolute overkill for that app. And just consider the setup nightmare. Sometimes creating setups is like building the universe. 7 days to see the light and you have to bring in everything. I really like some aspects of .NET and I want to move there in my own pace and where it makes sense. Being forced to move there really drives me crazy. I am a signature virus! Help me spread and copy me to your sig! Ooops I am infected
I'm curious what the problem is. The article doesn't say that ADO is going to go away. Your current code will still work with the latest MDAC. ADO just won't be upgraded any more, and I'm not sure what else they could add to ADO anyway. Michael :-)
-
I'm curious what the problem is. The article doesn't say that ADO is going to go away. Your current code will still work with the latest MDAC. ADO just won't be upgraded any more, and I'm not sure what else they could add to ADO anyway. Michael :-)
Michael P Butler wrote: The article doesn't say that ADO is going to go away. Your current code will still work with the latest MDAC. ADO just won't be upgraded any more, and I'm not sure what else they could add to ADO anyway. On that note what do people think of the new ADO.NET? I love the way it has seperated the database from the "recordset" so enabling disconnected recordsets (easily) and also working with an XML data source the same way as working with a SQL data source. Though I must admit the DataSet and other bits and bobs confused the hell out of me the first time I tried them. regards, Paul Watson Bluegrass Cape Town, South Africa "The greatest thing you will ever learn is to love, and be loved in return" - Moulin Rouge Martin Marvinski wrote: Unfortunatly Deep Throat isn't my cup of tea Do you Sonork? I do! 100.9903 Stormfront
-
SQL Server may be overkill but MSDE is not. It's based of the SQL Server engine but it is meant to replace Access/Jet. It's been around since SQL Server 7.0. It uses SQLOLEDB and is 100% compatible with SQL Server. Access is a horrible piece of crap. I know, I've worked with it extensively in the past so I don't have a probably with seeing support for it go. Jason Gerard
What platform would you recommend right now for someone setting up a small desktop db system for managing a small parts inventory? I've been approached by a local company to contract for doing that, I was going to simply recommend Access, as they already have Microsoft Office set up on their system. "Thank you, thank you very much" Elvis.
-
What platform would you recommend right now for someone setting up a small desktop db system for managing a small parts inventory? I've been approached by a local company to contract for doing that, I was going to simply recommend Access, as they already have Microsoft Office set up on their system. "Thank you, thank you very much" Elvis.
From what I've read, and the little bit I've worked with it MSDE would be great for what you're working on. I'm more concerned about what to do with smaller databases (like my internet links database program). MSDE is overkill for that, but the old fashioned text files are too slow.....
-
What platform would you recommend right now for someone setting up a small desktop db system for managing a small parts inventory? I've been approached by a local company to contract for doing that, I was going to simply recommend Access, as they already have Microsoft Office set up on their system. "Thank you, thank you very much" Elvis.
I would say. Stay away from the MSDE and use access. I’m not sure why some people have problems with it. If they need to store data, and they don't have a lot of data. Then they should use Access, otherwise SQL server. I have developed with both, and currently support both. Though is true that some access dbs are bad, but they are not bad because of access, but because whomever made the database was one of those fresh out of college, recently hired, went into IT because the pay is good, has not clue why anything happens in a program, uses access macros, don't know what RDBMS is, and works 9-5 (with 1 hour lunch break), baboons. Yes, we have some of these people here, and I hate them, every time one of them leaves, I feel like parting. MSDE is really slow, and if you are going to use msde, you might as well get yourself SQL server. Access is good if you need a lot of integration with the other office apps. Reporting, email, etc. Rodrigo.
-
Whats MDSE? I'm probably going to find out I've already stubled accoss it though - or am I? Giles
i think that's MS's new SQL Server Lite. it's the MicroSoft Data Engine: http://www.sqlmag.com/Articles/Index.cfm?ArticleID=7840 -c
-
I would say. Stay away from the MSDE and use access. I’m not sure why some people have problems with it. If they need to store data, and they don't have a lot of data. Then they should use Access, otherwise SQL server. I have developed with both, and currently support both. Though is true that some access dbs are bad, but they are not bad because of access, but because whomever made the database was one of those fresh out of college, recently hired, went into IT because the pay is good, has not clue why anything happens in a program, uses access macros, don't know what RDBMS is, and works 9-5 (with 1 hour lunch break), baboons. Yes, we have some of these people here, and I hate them, every time one of them leaves, I feel like parting. MSDE is really slow, and if you are going to use msde, you might as well get yourself SQL server. Access is good if you need a lot of integration with the other office apps. Reporting, email, etc. Rodrigo.
Using Access by itself is great, but... But with DAO and JET support dwindling, using an Access database from a program is questionable. (Having to distribute older database packages etc.)
-
I would say. Stay away from the MSDE and use access. I’m not sure why some people have problems with it. If they need to store data, and they don't have a lot of data. Then they should use Access, otherwise SQL server. I have developed with both, and currently support both. Though is true that some access dbs are bad, but they are not bad because of access, but because whomever made the database was one of those fresh out of college, recently hired, went into IT because the pay is good, has not clue why anything happens in a program, uses access macros, don't know what RDBMS is, and works 9-5 (with 1 hour lunch break), baboons. Yes, we have some of these people here, and I hate them, every time one of them leaves, I feel like parting. MSDE is really slow, and if you are going to use msde, you might as well get yourself SQL server. Access is good if you need a lot of integration with the other office apps. Reporting, email, etc. Rodrigo.
Thanks. I've actually done any number of smaller access database designs, with little problem. I've done a couple of SQL Server designs and would prefer it, but it is cost prohibitive to the customer for the size of their project. I just have not been keeping up with the evolution of the technology of late. "Thank you, thank you very much" Elvis.
-
Using Access by itself is great, but... But with DAO and JET support dwindling, using an Access database from a program is questionable. (Having to distribute older database packages etc.)
Right, but it all depends on what they want. If they want a small app that it is only going to be used for tracking (1-10 users). Then access is all you need. But if they want an app with a lot of users, and able to communicate with other systems (amybe even with a web interface), then you still use access but with ADO on the front end, or xml datadumps for your asp, or etc. Or go all out with sql server. At least until MS figures it out what they are doing with the msde. Or at least until the next release of sql server. (when sqlserver 2000 gets cheaper, or they ship a better msde). Rodrigo.
-
What platform would you recommend right now for someone setting up a small desktop db system for managing a small parts inventory? I've been approached by a local company to contract for doing that, I was going to simply recommend Access, as they already have Microsoft Office set up on their system. "Thank you, thank you very much" Elvis.
Access will do the job but it is a bit poor on the multi-user side. It's worth looking into the MSDE as it is pretty nice for smaller databases but gives the option to easily scale to SQL server. Michael :-)
-
Using Access by itself is great, but... But with DAO and JET support dwindling, using an Access database from a program is questionable. (Having to distribute older database packages etc.)
Have you ever tried JET through ADO? I think its great. James (2b || !2b)
-
Have you ever tried JET through ADO? I think its great. James (2b || !2b)
Most of what the BAs use is available thorugh DAO, and is easier for the Busines Analysts to learn (you really don't want them confused). Most of the new apps we are working on do use ADO, but we were really holding on until the .net release (no need to start new tools with old technology ;P ) I really don't use MSDE much, we do have a couple of apps that use it, but that was when we thought that msde was usefull, not anymore. Now, we stick with access, or with sql server. Rodrigo.
-
Thanks. I've actually done any number of smaller access database designs, with little problem. I've done a couple of SQL Server designs and would prefer it, but it is cost prohibitive to the customer for the size of their project. I just have not been keeping up with the evolution of the technology of late. "Thank you, thank you very much" Elvis.
I would say, that if you do a good database design, it won't matter as to wetter you do it in access or access with an msde back, or any other tool. If you need to move it to SQL server, you'll need to do work anyway. So long your structure is good; you won't need to change it, which will in turn make the rest easier. Rodrigo.