Hey Nick - thanks a lot for your code snippet, it works flawlessly! You have saved me a lot of time One more question - do you have any idea how can I get the IP address and physical address of the listed network cards?
Just so you know this is what Heath said to the last
guy that asked about getting certified in .Net.
Heath Stewart said
"Personally, I am not certified because I really don't want to be. I know a large number of people with certifications that know crap. They studied for the tests, memorized a few things, took the tests (sometimes a couple times) and got their certs. They're still idiots."
And this question prompted me to write in my personal message board on my profile page. I mean, he's going to get certified and doesn't even know how to find cert material? Every cert candidate should know about http://www.microsoft.com/traincert[^]!
Actually, a Jet database (.mdb file, which Access uses) doesn't require Microsoft Access at all. It simply uses the Microsoft Jet database engine that should be installed when you install MDAC 2.6 or higher, which is required for ADO.NET anyway. I might be wrong and it might be a separate download (they keep changing all that), but it'll be small and probably already installed because a lot of stuff uses it. That's probably the best database file you could use. With technologies behind it like DDL, you can even create a database from scratch, although shipping a .mdb file with a schema already created would probably be easier (almost like a template from which databases are created).
As far as SQL Server / MSDE go, this would be overkill for a simple checkboox application anyway. This is more for hard-pounding applications that need transactional services (not that a register wouldn't necessarily benefit from that), replication, user authentication and security, etc.). Besides, it's a big install and can be the cause of many headaches - especially for computer neophites.
If I want to sell this checkbook application - can I guarantee user's will have MDAC installed, and consequently, the Jet database?
If its small and redistributable, I don't mind bundling it - but I'm not sure Mr. John Doe is going to have ADO.NET installed (consequently MDAC and consequently JET) Is an MDAC installation the byproduct of a common application like IE or Office or something.
Also - you've described the database, but I'm a neophyte when it comes to connecting to .NET dbases. I am extremely familiar with JDBC. Is there a similar C# API?
From your description, I don't even think I have to "start" the Jet Database, I just need to find the set of classes that transparently access JET to read and write mdb files.
Is that conceptually correct?
I'll google around. Someone's bound to have an example. At least now I have an idea what I am looking for.
MDAC is the Microsoft Data Access Components, which include ADO, OLE DB, and ODBC. OLE DB providers are the "database drivers" which ADO.NET uses. Microsoft Jet is indeed a separate download, but is pretty small. See the Downloads section of the page linked above (which redirects, actually).
Without MDAC 2.6 or higher installed (MDAC 2.8 is the latest), you cannot use ADO.NET. The Microsoft Jet database engine installs the components necessary to use .mdb files. I'm not sure which one actually installs the Microsoft Jet OLE DB provider, but I'm betting it's the latter one.
MDAC will most likely be on the system. Less likely is that Jet will also be installed. Unfortunately, the .NET Framework setup includes neither technology ( ?). These aren't hard to package, though. The site I linked even discuss deployment.