If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#51
|
|||
|
|||
Opening Access db via DAO in vb.net
I don't expect they do, but their customers seem to think that's necessary.
-- __________________________________________________ ________________________ William R. Vaughn President and Founder Beta V Corporation Author, Mentor, Dad, Grandpa Microsoft MVP (425) 556-9205 (Pacific time) Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition) __________________________________________________ __________________________________________ "Arvin Meyer [MVP]" wrote in message ... "Spam Catcher" wrote in message . 1... "Arvin Meyer [MVP]" wrote in : I'm really sorry that you think that Access/JET is a single-user database. You're obviously missing giving some of your users a fast, easily maintainable solution. Microsoft thinks so too! Have you read their recent whitepapers? :-) Microsoft thinks that a million rows and 4000 columns are reasonable limits for spreadsheets too. Have you seen Excel 2007? -- Arvin Meyer, MCP, MVP http://www.datastrat.com http://www.mvps.org/access http://www.accessmvp.com |
#52
|
|||
|
|||
Opening Access db via DAO in vb.net
"William Vaughn" wrote
I don't expect they do, but their customers seem to think that's necessary. I know: The customer isn't always right, but, if the bills get paid, it's the customer who pays them. Even so, with the Mighty Microsoft Marketing Machine's golden tongues and the Mighty Microsoft Development and Support Machine's golden abilities, it would seem that Microsoft could have educated their customers instead of giving them a large coil of rope with which to hang themselves. I'm surprised, Bill, to hear this from someone who's sufficiently concerned about the quite stable, proven, and eminently usable Jet database engine that he thinks Microsoft ought to abandon it (for which read: take it away from their customers) and replace it with SQL Server. (I would hope you also think that they need to improve SQL Server whatever edition so that, to the end-user, it is equally as seamless to use as is Jet.) Larry Linson Microsoft Office Access MVP |
#53
|
|||
|
|||
Opening Access db via DAO in vb.net
Arvin makes some excellent points that are often lost on internal
folks at msft, especially the SQLS team. Bear in mind that each product team produces its own whitepapers in the hopes that providing detailed information about their product will not only help customers create successful solutions, but also increase the revenue stream for their product. Consciously or unconsciously, bias often creeps in, and in the case of the long-running Access/SQL feud, there has been a tendency to showcase the failure cases when Access was used inappropriately while ignoring the silent evidence of its spectacular success in creating real-world applications with a low TCO. So when reading whitepapers, it helps to keep an open mind and consider the source. The following paper was written by the president of FMS (an ISV creating Access/SQLS tools) and vetted by a member of the SQL Server team: Microsoft Access or SQL Server 2005: What's Right in Your Organization? http://www.microsoft.com/sql/solutio...or-access.mspx This one was written by an MVP and vetted by both the Access and SQL Server teams: Optimizing Microsoft Office Access Applications Linked to SQL Server http://msdn2.microsoft.com/en-us/library/bb188204.aspx Hope this helps shed some light on the subject while damping down the heat --Mary On Mon, 04 Feb 2008 18:44:49 GMT, Spam Catcher wrote: "Arvin Meyer [MVP]" wrote in : I'm really sorry that you think that Access/JET is a single-user database. You're obviously missing giving some of your users a fast, easily maintainable solution. Microsoft thinks so too! Have you read their recent whitepapers? :-) |
#54
|
|||
|
|||
Opening Access db via DAO in vb.net
To run synchronising on the backend db which is a replicated access database
"Norman Yuan" wrote in message ... With all other replies being post, I am just wondering: why on the earth do you need to use DAO in .NET? "John" wrote in message ... Hi In my vb.net app I am trying to open a db via DAO as below; Imports dao Dim dbSynch As dao.Database dbSynch = DBEngine(0).OpenDatabase("C:\MYDB.MDB") The problem is that on the last line I am getting the error 'DBEngine' is a type and cannot be used as an expression. What am I doing wrong? Many Thanks Regards |
Thread Tools | |
Display Modes | |
|
|