VB.NET Databindings

[marcf]

Hi everyone,

I've just studio using VS2008 and have a quick question regarding databindings, i'm fairly handy with vb6 so this question really relates to good practice rather than actual coding.

Our backend is SQL 2005 express edition, my application connects to this database fine, it is planned that the database will have approximately 10-20 users.

The application is basically a sales based CMS and I wanted to know if I should simply use the databindings as they are or create recordsets and have the users work off them?

It is possible that the forms will have 4/5 databindings each as our company has five major departments all of whom need access to the data and will be modifying it for their own purposes.

Currently the CMS is in access and is starting to become a little slow, hence the upgrade to VB.net/SQL server.

[dip_developer]

Hi everyone,

I've just studio using VS2008 and have a quick question regarding databindings, i'm fairly handy with vb6 so this question really relates to good practice rather than actual coding.

Our backend is SQL 2005 express edition, my application connects to this database fine, it is planned that the database will have approximately 10-20 users.

The application is basically a sales based CMS and I wanted to know if I should simply use the databindings as they are or create recordsets and have the users work off them?

It is possible that the forms will have 4/5 databindings each as our company has five major departments all of whom need access to the data and will be modifying it for their own purposes.

Currently the CMS is in access and is starting to become a little slow, hence the upgrade to VB.net/SQL server.

I did not understand what do u mean by
"simply use the databindings as they are or create recordsets and have the users work off them?"
and finally how your 10-20 users are working now while it is an access database??? how are u syncronising data of 5 different departments???

[marcf]

Sorry was trying to do too many things while posting this morning:

Databindings: As I understand it in vs2008 you link a form to data using the databindings. As the example when a user does next record if I use databindings the binding control then goes off and retrieves the next record from the database(or is the data retained locally unless its out of date?)?

If I create a recordset when I open the form then when the user does a next record on that then the data already exists on the client machine and it doesnt need to go off and get the new data?

What I am trying to avoid is masses of network traffic, I only want the clients to retrieve records from the SQL backend when the data is out of date.

The current database is a split access database, the five departments retrieve data that is relevant to them using queries and filters. Each department has its own front end and all access the same backend data.

Hope this clears things up a bit, dont worry too much about the existing access database and the new .NET application is intended to replace it. As I am learning VB.NET/VS2008 on the fly I was hoping for some advice as to the most efficient way of doing it. The last thing I want is to spend a month creating this new system and it to be slow navigating/adding records.