I am very new to programming etc so I may be misunderstanding the situation, but my question is this:
VB.Net Express is a programming language which comes with database functionality via SQL Server Express, whereas Access is a Database which is programmable via VBA.
So, if one is developing a (fairly simple) database based application what are the pros and cons of using one set of software tools versus the other
Thanks for any insights.
Eric

VB + SQL server vs Access
kapicou
hi,
the main point for me is the requirment , if you used sqlserver that will need your client to have sqlserver program what will take much resources , but if you used msaccess your client shouldn't have access to run your program
so if you write simple application for personal use then access or even xml is better , but if you build a big program i mean very big then sql server is better (accept much more connections, faster, and stable)
so it depends on what you gonna do
hope this helps
G Unot!
Isn't it free to distribute an mdb file
I agree re: scalability ( obviously )
I still would say that distributing an mdb is easier than installing SQL Express, although I deploy MSDE with my app, and I use a named instance to get around potential problems.
Access is certainly the 'wave of the past', I personally do not use it, but I still think it has it's place with smaller apps that want to be able to deploy by zipping and copying a folder.
nonoandy
Hi cgraus
I think you are Wrong..... With one Click Deployment Access and SQL Express install equally the SAME....... If this is true which one would you CHOOSE access or SQL Express One of us is definetly Wrong...... Would Some One Jump in Here and state which is TRUE..... Thanks
Doeb
http://msdn.microsoft.com/vstudio/express/sql/
Cheers
Driescox
It really depends on your field of expertise. Personally, I'd crank out something faster using C# and SQL Server, because that's what I do. But, Access is definately easier to deploy, and if it's a good enough database for the job at hand, it may also be easier to learn as it appears to me to be more wizard based.
Finally, there are bound to be some things that Access cannot do, but if you're doing a simple database, I'm sure you won't find any of it's limitations.
ronGot
I downloaded it from there, when I verified that it does indeed install a seperate application on your hard drive. Was there a bit in there that you wanted me to read I read most of it before replying to you before.
James Kovacs
" SQL Server Express is Free..... Access Is NOT Free..... "
You've moved into an interesting domain.
The Access program is not free. But you can certainly create,use and deploy Access projects to systems that don't have ACCESS software and they will sure run. I only use the program to insure that my software is doing what I think it is.
I don't program in VBA or VB6 anymore and do most of my programming with ADO.NET.
For programming, all you really need is MDAC 2.8 which is installed with XP SP2.
I believe you can create ACCESS DataBases with DAO and I'm not sure about ADO. ADO.NET is really an in memory system. I think it's a little weak on the I/O side. To persist Tables and Columns I use ADOX in conjunction with ADO.NET.
Futura57
Hi Billy.
SQL Express is the new MSDE, as far as I can see. Regardless of how easy deployment may be, I don't see how it can work without installing a seperate database program, which will require more complex connection strings than Access, and which will be a seperate process ( a windows service in fact ) that your app relies upon. Now, this is hardly the end of the world, but it *is* more complex than having all the logic in your code or the libraries installed with Windows, and just copying an MDB file around the place. If you install SQL Express, your database is not in the same directory as your application.
So, I'm largely with you, in that I'd vote against Access almost all the time. But, I still do believe there are valid reasons to consider Access for smaller programs, especially self contained ones ( that is, they get installed and only ever interact with the local user/desktop ).
uzy
Sajal57918
If you mean the same from the end users point of view, that may be true, so long as they don't try to copy the app to another machine by copying the folder. However, to use the Access engine, an app needs merely to have an .mdb file, you don't need to install Access, the application. No matter what One Click does, it is simplifying the task of installing a seperate app, in a different folder to the app that uses SQL Express. In that point, they are different. If you mean that One Click makes it so easy that it's virtually the same, that may be true. But, the difference that I was highlighting is definately the case, in fact, this is why they need One Click to move the database between machines.
Hugo from Holland
Puneet Minda
Randy Trihydro
Abort Syntax
first of all access never been a wave it was always tool like text editor there have been always databases better than access to use the only advance for access it was easy to use
about microsoft want you to learn .... if someone want you to choose something you don't think its the best choice for your situation.. you going to choose it
sqlserver is powerfull should be used in powerfull program not for personal diary for example.you have to learn it first . because i'm still learning and all what i write is small programs i don't need to learn sqlserver now for 2 reasons 1) to concentrate in vs first and don't confuse myself 2) i don't write something deserver powerfull tool
i think if you gonna impose sqlserver on your client that have personal pc you will write programs for yourself or you have to ship extra rams with you programs
best regards