Keeping data synchronized accross users

%3CLINGO-SUB%20id%3D%22lingo-sub-1454004%22%20slang%3D%22en-US%22%3EKeeping%20data%20synchronized%20accross%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1454004%22%20slang%3D%22en-US%22%3E%3CP%3EHope%20I'm%20posting%20my%20question%20to%20the%20right%20place%3F%3C%2FP%3E%3CP%3EI'm%20new%20to%20SQL%20Server.%20I%20have%20a%20project%20to%20migrate%20an%20MS-Access%20small%20database%20to%20SQL%20Server.%20So%20far%20so%20good%2C%20except%20I%20am%20running%20into%20the%20problem%20of%20keeping%20data%20synchronized%20across%20connected%20users%20such%20that%2C%20if%20UserA%20creates%20a%20new%20record%2C%20UserB%20won't%20know%20until%20he%20%22refreshes%22%20his%20copy%20of%20the%20database.%20I'm%20using%20VisualBasic%20with%20TableAdapters.%20Right%20now%2C%20because%20of%20testing%20limitations%2C%20I%20created%20ONE%20single%20SQL%20Server%20Login%20(UserID%3D%20XXX%20and%20UserPassword%20%3D%20YYY).%20What%20happens%20is%20that%20my%20application%20is%20installed%20on%20a%20number%20of%20stations%20on%20the%20network%20and%20everyone%20is%20connecting%20with%20the%20same%20credentials.%20This%20%22model%22%20works%20fine%20until%20each%20users%20starts%20to%20add%2C%20modify%2C%20update%20and%20delete.%26nbsp%3B%3C%2FP%3E%3CP%3EI%20suspect%20I%20ought%20to%20switch%20Authentication%20models%20and%20use%20Windows%20Authentication%20to%20access%20the%20server%2C%20as%20a%20first%20step%3F%20But%20I%20have%20no%20idea%20how%20that%20will%20fix%20the%20'synchronization'%20issue%3F%20I%20suspect%20some%20kind%20of%20communication%20%22mechanism%22%20has%20to%20go%20on%20between%20%22connected%22%20users%3F%20But%2C%20to%20the%20best%20of%20my%20understanding%2C%20using%20TableAdapters%20and%20DataSets%2C%20I'm%20in%20a%20%22disconnected%22%20mode.%20I%20don't%20know%20the%20limit%20of%20this%20model%20and%20whether%20to%20give%20each%20users%20separate%20account%20will%20help%20at%20all%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20was%20thinking%20about%20adding%20a%20Timer%20to%20my%20application%20and%20issue%20a%20%22refresh%22%20every%2010%20minutes%20or%20so%2C%20like%20this%20%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3EMe.ProductTableAdapter.Fill(Me.SQLDataSet.Products)%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3EAny%20help%20is%20appreciated.%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hope I'm posting my question to the right place?

I'm new to SQL Server. I have a project to migrate an MS-Access small database to SQL Server. So far so good, except I am running into the problem of keeping data synchronized across connected users such that, if UserA creates a new record, UserB won't know until he "refreshes" his copy of the database. I'm using VisualBasic with TableAdapters. Right now, because of testing limitations, I created ONE single SQL Server Login (UserID= XXX and UserPassword = YYY). What happens is that my application is installed on a number of stations on the network and everyone is connecting with the same credentials. This "model" works fine until each users starts to add, modify, update and delete. 

I suspect I ought to switch Authentication models and use Windows Authentication to access the server, as a first step? But I have no idea how that will fix the 'synchronization' issue? I suspect some kind of communication "mechanism" has to go on between "connected" users? But, to the best of my understanding, using TableAdapters and DataSets, I'm in a "disconnected" mode. I don't know the limit of this model and whether to give each users separate account will help at all?

 

I was thinking about adding a Timer to my application and issue a "refresh" every 10 minutes or so, like this :

 

Me.ProductTableAdapter.Fill(Me.SQLDataSet.Products)

 

Any help is appreciated.

 

0 Replies