Re: MS Access DAO -> ADO.NET Migration
- From: "William \(Bill\) Vaughn" <billvaRemoveThis@xxxxxxxxxx>
- Date: Tue, 21 Nov 2006 09:18:14 -0800
I'm checking with Peter about the zip file distribution. It was supposed to
go out with the book.
See >>> below
--
____________________________________
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)
-----------------------------------------------------------------------------------------------------------------------
"Garry" <garrygrolman@xxxxxxxxx> wrote in message
news:OtmlIgVDHHA.3676@xxxxxxxxxxxxxxxxxxxxxxx
EBook is interesting and certainly fills in a lot of 'hidden info' on the
SSCE BUT, the zip file of the code in the ebook iz missing.
HowDoIGetIt????
The GUID seems such a HEAVY THINGY for lowly auto-increment need. It
doesnt tell me anything about in what order the records were originally
created and is very taxing to verbalise its content to someone over the
phone. My usual records/DataRows have an auto-increment for the first
column AND, possibly, a unique identifier that I generate per database and
possibly, per table.
I agree. In SQL Server (the real one) there is a way to create a
sequential GUID that solves the first problem, but not the second...
I turn your attention to a similar thingy with VB.NET where INI files are
not supported directly because Microsoft wants us to use XML format files
for this info. WHY make things more difficult. In VB6, they wanted us to
use the registry instead of INI files and now they want us, developers, to
use XML formatted files.
Remember the word KISS.
Of course. And, no MS seems to do what they think is best (in a kinda
pedantic way).
The book was a pleasure to read after the gibberish that Microsoft 'puts
out'. However, SQL Server Management Studio is nowhere to be found on my
machines and the msi will not install, dissappearing without a trace at
the end of 'configuring' files. No message. Nothing. I feel that I am not
alone in this and your book's content, in a large part, is based on this.
SSMS can be installed for free via the SQL Server Express Advanced
Services SKU (with the toolkit) or via the Developer Edition. It does
not come with the ordinary SQL Server Express SKU. I have not heard of
other installation issues.
My basic inclinations are always to use code anyway. Something I learned
from trying to use the Data Tools in the first edition of VB6 7 odd years
ago.
Not a bad idea, but the tools can help. As I show in the book, using
scripts for the DDL is possible and pragmatic.
My migration app works building a SSCE database file with imported data
from scratch in code using a source MDB. But, only the tables and some
data types which I do not use, may not be supported
The trick is to convert to "equivalent" types.
hth
Garry
"William (Bill) Vaughn" <billvaRemoveThis@xxxxxxxxxx> wrote in message
news:enbeq$ADHHA.4280@xxxxxxxxxxxxxxxxxxxxxxx
Frankly, (as I discuss in the book), I leaning away from Identity
(autoincrement) columns for a number of reasons. While these are
supported in SQLCe, there are situations where its SQL is too limited to
permit proper management and importing data with pre-assigned Identity
columns. I think that GUIDs (UniqueIdentifiers) make more sense for many
of these databases. This approach also works better when replicating the
database (which does not support Identity columns).
As far as getting VB to recognize the identity property of an Access/JET
database, I'm at a loss--sorry.
--
____________________________________
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)
-----------------------------------------------------------------------------------------------------------------------
"Garry" <garrygrolman@xxxxxxxxx> wrote in message
news:eTKvxZ$CHHA.3228@xxxxxxxxxxxxxxxxxxxxxxx
Framework 2
SQLCE 3.1 (Newest available - I think)
VS2005 Service pack Beta
Bought the book before I read your email.
The database is now copied with all the Data fields and values BUT, the
Primary key, AutoNumber is 'fudged' since in all my Access tables, the
first field, usually fldItemID, is the primary key and is an autonumber.
In the code, I know which is the first field.
The vb code does not manage to detect those specific properties.
field.Properties("ISAUTOINCREMENT").Value always equals False and so
does "KEYCOLUMN" even when I know that they are autonumber and
PrimaryKey.
Any solution??
Garry
"William (Bill) Vaughn" <billvaRemoveThis@xxxxxxxxxx> wrote in message
news:ON7skO$CHHA.4620@xxxxxxxxxxxxxxxxxxxxxxx
The SQLCe engine requires the 2.0 Framework. Do you have that
installed? What version of Visual Studio and SQL Server is installed? I
built database tables from scripts and wrote my own batch processor to
run them. These are included in the EBook examples.
hth
--
____________________________________
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)
-----------------------------------------------------------------------------------------------------------------------
"Garry" <garrygrolman@xxxxxxxxx> wrote in message
news:O9uVYB8CHHA.3836@xxxxxxxxxxxxxxxxxxxxxxx
Bill,
Perhaps you have an answer to the post two lines up.
I have other problems concerning the actual updating of data from my
accumulating DataTable but the basics of defining the tables with
attendant columns in a new SSCE data base are still not completely
solved. However, it does build the SSCE database, just some of the
definitions are not included.
Also, SSEv31VSTools-ENU.exe with the SQL data management utilities
will simply not install on my machine.
Garry
"William (Bill) Vaughn" <billvaRemoveThis@xxxxxxxxxx> wrote in message
news:u%23yx11zCHHA.4680@xxxxxxxxxxxxxxxxxxxxxxx
I also share your frustration with the Microsoft doc. You'll also find
that Intellisense does not help either. That's because it leads you to
think that specific types, methods, properties and events are exposed
when they are not--you won't find out until runtime. To deal with this
issue, I wrote my first EBook that walks through the entire namespace
and documents how it really works. It's written for developers that
are somewhat familiar with the SqlClient namespace and ADO.NET in
general (and those that have read my Hitchhiker's Guide to Visual
Studio and SQL Server book. This book is available at
http://www.hitchhikerguides.net/EBooks/Titles/5582.aspx.
Incidentally, Microsoft chose to change the name from SQL Server
Everywhere Edition to SQL Server 2005 Compact Edition about three
weeks ago. This version of the SQLCe DBMS engine has been tuned to
run in a Windows Forms environment. It's a fully relational database
that supports a subset of the TSQL SQL syntax. It's easy to deploy
(just copy 6 DLLs), is fully encryptable (so it's safer for data you
take to the field) and has twice the capacity of JET (4GB). SQLCe is
also designed to act as a Subscriber to a SQL Server-hosted
Publication. This can make it even easier to construct a distributed
architecture around SQLCe. MS is still doing work on the Visual
Studio and SQL Server Enterprise Manager development tools but the
EBook shows how to get around these limitations until the next SP or
Orcas ships.
Early next year, I'll be publishing the next in my series of EBooks.
This time on SQLCe Replication. I'm waiting for MS to finish work on
a new replication scheme that promises to be easier to use than their
current approaches.
--
____________________________________
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)
-----------------------------------------------------------------------------------------------------------------------
"Garry" <garrygrolman@xxxxxxxxx> wrote in message
news:%23SURfWtCHHA.4928@xxxxxxxxxxxxxxxxxxxxxxx
I had your problem basically and am working at the moment to transfer
existing Access 97 databases, (with data), to SQL Server Everywhere,
the new/old database referred to by William (Bill) Vaughn. He
suggested to me that I use this new database for .NET 2005
development where the DataBase requirements are similar to what I had
in a VB6/Access97 desktop application.
I am working on an app to migrate the Access 97 database to the SSEv
database and it is going relatively smoothly. Although, there are
some problems as I have defined in a post a little above yours.
I do not expect to edit relationships within the predefined database
OR re-define existing tables BUT, I have seen reference to code
which can do this.
If you try to find code samples - do yourself a favor, use Google as
William (Bill) Vaughn valiantly suggests. Microsoft help is, in many
cases, gibberish, which will not solve your query and will just make
you angry and frustrated. I wonder when Microsoft will catch on a
construct a serious library of code samples instead of the meager
offerings available.
If any of the Google search results take you to forums which require
that you 'join', be careful. Some of these forums even want you to
pay to join without you knowing if a solution is actually available
there.
Be careful about using Sponsored Links as these must have some
financial incentives involved otherwise they would not be there. It
costs money to put a Sponsored Link on a Google Search result page.
Every click means that money is earned by Google.
If you want to go down this route, use 'Reply to Sender' as well as
'Reply to group' and I will send you my code which is a near
completed application in VB.NET. I do not want to post my email
address here.
I need an exchange of info and opinions from another programmer who
is having similar, if not identical problems.
Garry
<moomoofatcow@xxxxxxxxxxx> wrote in message
news:1163796070.268114.323610@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have an VB6 program that I wrote that access Microsoft Access
databases using DAO. DAO has methods and properties that are Access
specific (such as viewing and editing relationships or indexes on
the
tables) I want to write a new version of the program in VB 2005,
and I
want to use ADO.NET to access the data. Are there ways of changing
the
indexes or relationships of the MS Access database using ADO.NET?
Or do
I still need to use DAO to perform these operations?
As a side note, with a few tests that I've done already with some
queries, it seems like DAO is much faster than ADO.NET at running
queries and returning results. I am using the DataReader...does
anyone
have any information about the differences etc? Thanks in
advance...
.
- References:
- MS Access DAO -> ADO.NET Migration
- From: moomoofatcow
- Re: MS Access DAO -> ADO.NET Migration
- From: Garry
- Re: MS Access DAO -> ADO.NET Migration
- From: William \(Bill\) Vaughn
- Re: MS Access DAO -> ADO.NET Migration
- From: Garry
- Re: MS Access DAO -> ADO.NET Migration
- From: William \(Bill\) Vaughn
- Re: MS Access DAO -> ADO.NET Migration
- From: Garry
- Re: MS Access DAO -> ADO.NET Migration
- From: William \(Bill\) Vaughn
- Re: MS Access DAO -> ADO.NET Migration
- From: Garry
- MS Access DAO -> ADO.NET Migration
- Prev by Date: Re: DataView.Find not working with GUID
- Next by Date: Re: Connection String - how to include timeout?
- Previous by thread: Re: MS Access DAO -> ADO.NET Migration
- Next by thread: Re: MS Access DAO -> ADO.NET Migration
- Index(es):
Relevant Pages
|