Hello CypherDrive,
For your request of the examples to access Microsoft Access database with
VB.NET:
*Walkthrough: Editing an Access Database with ADO.NET*
http://msdn.microsoft.com/en-us/library/ms971485.aspx
This is a general introduction of Access database - ADO.NET (can be written
in VB.NET). However, this article directly uses SQL commands to update
database instead of a DataSet.
*ADO.NET: Update a Database from a DataSet*
http://asp.dotnetheaven.com/howto/doc/adoplus/UpdateDataFromDB.aspx
This introduces how to update a database from a DataSet. Although the demo
uses SQL Server database, as Cor said, the only difference between a Jet
DataBase and a SQL Server database with ADO.NET is we need to use the OleDB
namespace instead of the SqlClient namespace.
In order to resolve the ID Uniqueness in case there are multiple users
accessing and updating the same table, we may refer to the Data Concurrency
support in ADO.NET:
http://msdn.microsoft.com/en-us/library/cs6hb8k4(VS.80).aspx
By default Visual Studio creates these parameters for you if you select the
Optimistic Concurrency option in the DataAdapter Configuration Wizard. It
is up to you to add code to handle the errors based upon your own business
requirements. ADO.NET provides a DBConcurrencyException object that returns
the row that violates the concurrency rules.
Please let me know if you have any other concerns, or need anything else.
Regards,
Jialiang Ge (
[email protected], remove 'online.')
Microsoft Online Community Support
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
