asked on

SQL R22008 Vs MS Access Everyone Connected can not see changes

I am new to SQL. I importated my DB in MS SQL 2008 R2. Everything went fine. I am storing rows a data on a grid. When a user clicks the grid it put the user name in a cell. When the user moves off of the row the cell on the grid gets updated to blank. All users that are coinnected to the Acess data base see the chantges without doing anything special. But MS SQL 2008 R2 does not broadcast those changes. Can anyone tell me why? I just do not get it. I would think that is what you would want a data base to do. Is show everyone the changes immedialty.

DESPERATE

ASKER CERTIFIED SOLUTION

Ryan McCauley

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

MKadric

ASKER

1) When I say broadcast changes. On the SQL server version the DB is updated but any client computer that is connected to the DB at the time of update those updates are not shown.,

2) ACCESS is the first veriosn and it works correctly.

4) SQL is one version and MS ACCESS is another version.. Same code jus differenct connection strings.

5) Access is standalone.

Ryan McCauley

So the SQL database gets updated, but the clients with data on their screen don't get the updates? If they close their screen and re-open it, do they see the updated data then, or do they still show old data? It's possible that the update is working properly, but where Access might have somehow notified users that there was new data, SQL Server doesn't have that kind of functionality - all events are driven by client requests. I'm not sure, but Access forms may detect that the underlying data has changed and trigger a refresh.

MKadric

ASKER

Correct (So the SQL database gets updated, but the clients with data on their screen don't get the updates)

If I do a requiry then the updates are there or if they re open applicaiton. This is so totally unexceptable. When I requery the screen flashes. I have to remember what row they were on in the grid, requery and put them back on the same row.

I do nothing special in MSAccess. It just does it... Just like MSSQL Should.
I would think that MSSQL is far more brighter than MSACCESS

Anthony Perkins

>>I do nothing special in MSAccess. It just does it... Just like MSSQL Should. <<
That is a very bad assumption. They are totally different animals, expecting SQL Server or Oracle or MySQL for that matter to work the same as a file based database that relies on client based resultsets is naive to say the least.

>>I would think that MSSQL is far more brighter than MSACCESS <<
Only if you develop taking advantage of its functionality, otherwise it is just as dumb as MS Access if not worse.

Ryan McCauley

MSSQL and Access, though both with database functionality, are two completely different systems - Access is an application designed for viewing and manipulating data, and SQL Server is designed to store vast amounts of it. The "automatic refreshing" feature in Access doesn't exist in SQL Server because MSSQL just stores the data - the application you've written on top of it is what needs to refresh the data.

If you're using a datagrid and you need to refresh the whole thing, then you're at a loss - you'll have to remember which line they're on, refresh the grid, and then put them back.

Another option may be to fetch the data for their current line in the background, without refreshing the grid - compare it to what's in the grid currently, and if they're different, refresh the grid (or just update the row they're on).