Database apps that are integrated into VS.Net - Opinons

[windsailor]

I am looking for a Database app. that I can use with Visual Studio.Net (VB.Net) and is preferrably integrated into Visual Studio. I am gearing for a desktop database, basically single user, with an option to expand later into the internet. A small footprint is desired (because of distribution possibly over the net), .Net compatible and robust (MSDE is way too big, and Access just isn't enough). XML is out, I want to be able to save pictures etc.

I am moving from Access to VB.Net which is quite a jump and was hoping to get some advice. Any and all advice is greatly appreciated!

Thanks

 

[Dimandja]

You are confusing Access - a database management system -with Visual Studio, which is a software development environment.

You can't "move" from Access to VB.NET. You can "move" from Visual Basic (insert version here) to Visual Basic .NET. As there is no "integrated" database in Visual Basic, there is none in VB.NET.

The Access database (not VBA - which IS integrated into Access) accessed by VB.NET, is still good enough for the stated purpose.

Dimandja

 

[skiflyer]

Actually I disagree. Access is both a database and a limited functionallity front end for said database. Many people create fairly complex programs in access which can be moved to another language.

.NET is a fine front end, I'd personally plug it into either MSDE or MySQL if I were you.

 

[windsailor]

Access has a lot of version problems that involve operating systems and actual versions of Access. Currently I use Office 2003 and work with Access projects as a hobby to write apps for friends.

I didn't want to distribute the runtime because of the size of the download (working on a possibility of selling the application through the internet) and the inherent issues with the jet database (there are ways to circumvent security issues with the jet database). MSDE is way too big to distribute as a download for an application via the internet and there may be installation issues with people that know very little about such things.

I know what Access, VBA, and what .Net is, well, I have a understanding what .Net is. I have VS.Net 2003 and I am learning VB.Net, ADO etc. The move from Access and VBA to the .Net environment was to enhance my skills and programming options associated with .Net. Access is a good starting place to learn relational database practices, but once you start tweaking it in VBA there are exceptions on what will run on different environments. In my opinion you can create very complicated apps in Access, but you have to stay confined to the limitations of the engine, once you start tweaking in VBA to the make the engine groan, you start running into issues. I like the concept of .Net and its libraries, although I really haven't distributed any apps in that environment to see if it has issues similar to Access.

When I said integrated, I simply meant to have an Ole DB driver listed in VS.Net etc. to utilize more native options inside of Visual Studio.Net.

I have recently bought VistaDB and working with them on the final release (although I consider myself a hobbiest, not a professional - I have a lot to learn!), other options were TurboDB, Valetina etc. These were the some of the programs or databases I originally was looking into to work with VS.Net.

The other thing that was thrown around on the internet was that maybe the 2003 jet database would possibly be the last released version (dumping the Jet engine), moving to MSDE. So I didn't want to stay with an engine that would soon retire...

So I was left to hunt for a replacement for what I should have said in the beginning was the jet engine...

I will look into MySQL also... just wanted to know if someone had or is going through a similar experience...

Thanks

 

[skiflyer]

I hear you, watched a company go through the same thinking... what to do for users who don't want to run a SQL Server... distributed over the internet etc etc... they settled on MSDE as a FYI...

But depending on just what you need, you sound like you may be a perfect candidate for SQLite

http://www.sqlite.org/

This page should help you decide...

http://www.sqlite.org/cvstrac/wiki?p=WhenToUseSqlite

And it's in the public domain so any and all use of it is completely free.