Re: Using MS Access in ADO.NET - coming from VB6
- From: "Garry" <garrygrolman@xxxxxxxxx>
- Date: Sun, 5 Nov 2006 19:16:26 +0200
First - thank you for answering my post
I, as a new .NET programmer, am rather sceptical about anything new from
Microsoft and its claims are often forgotten after a relatively short period
of time. Remember the Microsoft promise to make a fully compatible Dot NET
framework available for other operating systems, Linux for instance or Mac
computers making the DotNET languages fully cross platform.
I have yet to see one of these announced.
That SQL Server 2005 Compact Edition is free is good.
That it can be easily installed simply by copying DLLs to the target machine
is good. (Yet to be tested and seen)
Duz it have a utility that will let me see the tables and their content or
must I write an appropriate generic utility for this.
Is there a utility to define tables - as in MS Access.
First editions from Microsoft are, sadly, usually half-baked and I need a
mature data base to re-write/base my very much data orientated application.
Why is Microsoft not fully supporting MS Access - a mature and well tried
data base which is excellent for stand-alone applications as mine is.
Thanks again for your suggestion. I do not reject it - I am just skeptical
of the claims and rather disheartened at finding constant obsticals to
re-writing my large VB6 application in DotNET.
Garry
"William (Bill) Vaughn" <billvaRemoveThis@xxxxxxxxxx> wrote in message
news:%23%23UAUaPAHHA.3560@xxxxxxxxxxxxxxxxxxxxxxx
Cor is right, but there is another choice for a secure DBMS engine that
even my daughter Fred could install: SQL Server 2005 Compact Edition. It
can be installed by copying the DLLs along with the application DLLs and
other executables directly to the user's system. The Compact Edition (the
DBMS formerly known as SQL Everywhere, SQL Mobile and SQLCE) is a
lightweight DBMS engine that is fully encryptable and not subject to the
shared file or MDAC issues you'll encounter with JET (the Access DBMS).
It's a single-user DBMS that strips off the features that only multi-user
or larger database DBMSs require so its very (very) fast. It can be
programmed in many ways similar to SqlClient. I'm working on a new
property management application based on it. It's also free. It should be
released next week along with my EBook on the subject. See
www.hitchhikerguides.net for more information.
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no
rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
Between now and Nov. 6th 2006 you can sign up for a substantial discount.
Look for the "Early Bird" discount checkbox on the registration form...
-----------------------------------------------------------------------------------------------------------------------
"Garry" <garrygrolman@xxxxxxxxx> wrote in message
news:OiIRzXKAHHA.4992@xxxxxxxxxxxxxxxxxxxxxxx
One of the annoying problems of distributing my VB6 MS Access orientated
financial application to paying customers was that there were many
problems with the MDac installations which caused the application to
crash..
Mostly they could be solved by telling the customer to download the
latest MDac and installing it.
Others were not so lucky and our application was discarded on that
computer.
If, when re-writing code in VB.NET, I use similar code to make an ADODB
connection and then use the .NET objects, DataTable, DataSet and Adapter
etc, is all the 'behind' support coming from the DOTNET FrameWork??? Is
it independant of any MDac installations?????
In other words, am I still going to have the same problems with Data
Access in DOTNET which are caused by inncorrectly installed or
incompatible ADO components????
I do not want to use SQL!
Garry
.
- Follow-Ups:
- Re: Using MS Access in ADO.NET - coming from VB6
- From: William \(Bill\) Vaughn
- Re: Using MS Access in ADO.NET - coming from VB6
- From: Robert Simpson
- Re: Using MS Access in ADO.NET - coming from VB6
- References:
- Using MS Access in ADO.NET - coming from VB6
- From: Garry
- Re: Using MS Access in ADO.NET - coming from VB6
- From: William \(Bill\) Vaughn
- Using MS Access in ADO.NET - coming from VB6
- Prev by Date: Re: Using MS Access in ADO.NET - coming from VB6
- Next by Date: Re: Using MS Access in ADO.NET - coming from VB6
- Previous by thread: Re: Using MS Access in ADO.NET - coming from VB6
- Next by thread: Re: Using MS Access in ADO.NET - coming from VB6
- Index(es):
Relevant Pages
|