September 2006 Archives

A recent question on the newsgroups asked about the life-expectancy of DAO and if it makes sense to transition to ADO to access their database.

The problem here is not DAO or even ADO classic (COM-based ADO). The problem here is the JET engine.
When you write an application using JET whether you you Access or VB6 or VB.NET or any other language, you are limited by the capacity and architecture of the shared-file architecture of JET. Your security is limited by JET's inability to be encrypted and since by its very nature it's designed to be passed around as a file and accessed by whomever receives it, it should not contain private data. Sure, there are lots of situations where a DBMS as simple as JET is okay--as in the home or for some non-secure office applications. But IMHO, JET is really not suitable for businesses that need to pass manage secure data. We've talked about and debated the merits and foibles of JET for many years here on this newsgroup and in other forums.

I'll be working with the folks at SetFocus to present an 8-hour seminar on ADO.NET 2.0 Architecture and Best Practices. It's one of the "The Guy Who Wrote the Book" series. Basically, the attendees can be anywhere on the planet (except parts of Cleveland). They run Polycom's PVX (or somesuch) software on their systems--using a web-cam to show their face to the instructor (me). On my end I see all of the students (limited to about a dozen) so I can see if they have questions or have fallen asleep.
This talk is similar to the session I give at major conferences--but updated with the latest on SQL Server Everywhere and other emerging technologies. Given the small class size, there will be plenty of time for individual Q&A. I’m sure you’ll enjoy it. Know someone who needs this? Get signed up soon they have just opened registration and there aren’t many seats available.

Another question came up in the newsgroups today that's been asked (and answered) before so to short-circuit having to repeat myself, here is a blocl of code that can be used to enumerate the providers on a system and the services that the provider can see on the network. In other words, it lists the SQL Server instances on the network and puts the list in a DataGridView.

This code is extracted from an example in my new book Hitchhiker's Guide to Visual Studio and SQL Server due to be on the streets in early November. See for more information.

The Question:

I am writing a database application for use in disconnected situations. The application will be installed on laptops. The intention is for the users to connect to the central SQL Server 2000 database, get the data, then go into the field and use it. They may be disconnected for several days. They data needs to persist through application closings, power offs, etc. When they are done, they will reconnect and their changes will be sent back to the database. I am new to .NET, so am looking for some advice on how to best approach this. Thanks <name withheld>



Powered by Movable Type 4.21-en

About this Archive

This page is an archive of entries from September 2006 listed from newest to oldest.

August 2006 is the previous archive.

November 2006 is the next archive.

Find recent content on the main index or look in the archives to find all content.