[RESOLVED] Moving from VB6 to VB.NET have some questions about Sql and ADO etc

[jmcilhinney]

All ADO.NET works the same way no matter the platform or data source. You create a Connection with a connection string to handle connecting to the database. You create a Command to execute an SQL statement over the connection. You create a DataAdapter to encapsulate all the Commands that will operate on a single table. A DataTable is used to store data locally and a DataSet is used to store multiple tables and the relationships between them.

[easymoney]

All ADO.NET works the same way no matter the platform or data source. You create a Connection with a connection string to handle connecting to the database. You create a Command to execute an SQL statement over the connection. You create a DataAdapter to encapsulate all the Commands that will operate on a single table. A DataTable is used to store data locally and a DataSet is used to store multiple tables and the relationships between them.

Thanks. That was a very helpful clarification, thanks for filling in the gap. It is starting to make sense now.

[easymoney]

Of course my primary goal for this app is for it to deploy a back-end Sql Server 2005 server running on a dedicated machine. The VB front end will run from client workstations on a local network.

I assume for now I should start with Sql Server 2005 Express for the development phase. Is it lightweight enough to run with VS 2005 ide on the local machine vs full blown Sql server connecting across a network?

Sadly, I am attempting to migrate a large MDB access file to Sql. Currently the application authorization process is merely usernames and passwords stores in an un-encrypted file shared on a network drive. It works ok for 4 or 5 users, but of course any one on the network could simply edit the db or even delete the entire file.

I need to nail down a process and model for preventing the types of actions. So on top of Domain based user security, I need db connection via IP and server based security. Utimately I need the application to have the ability to log each users login info, accounts accessed, data changed, etc and also lockout users during critical process or db updates. I would like to allow the app security to have user and group access to limit data access based on username and password vs total server administration.

Finally on the wishlist is the ability for parts of the db be exported to a webserver so that basic functions can be accessed from the web. Now lets backup into reality at this very moment.....

For now, it is just basic data access and creating a working model, but what should the roadmap look like to at least start in the right direction? Any insight anyone... TIA