Thom
Nov 24th, 2000, 09:07 AM
Has ANYONE ever used this property, or the
Jet OLEDB:Locking Granularity propery of the connection object to LOCK access to a table in an A2K database?
From what MSDN sez, the Connection Control property determines if users will be prevented from connecting to a database; and IF the property Value = 1 no other user can connect.
So in theory, if I have an Admin open a connection with a Connection Control value=1 and then LEAVE the connection OPEN while he's working on the specific table-NO ONE else can connect to the DB-right? This may seem bad, but it actually SEEMS to ensure that no users can be taking tests while the admin is changing/adding to them. Anyone ever get this to work this way??? <g>. I'd appreciate ANY help-this is the LAST issue I have to resolve to finally get this sucker done!
Jet OLEDB:Locking Granularity propery of the connection object to LOCK access to a table in an A2K database?
From what MSDN sez, the Connection Control property determines if users will be prevented from connecting to a database; and IF the property Value = 1 no other user can connect.
So in theory, if I have an Admin open a connection with a Connection Control value=1 and then LEAVE the connection OPEN while he's working on the specific table-NO ONE else can connect to the DB-right? This may seem bad, but it actually SEEMS to ensure that no users can be taking tests while the admin is changing/adding to them. Anyone ever get this to work this way??? <g>. I'd appreciate ANY help-this is the LAST issue I have to resolve to finally get this sucker done!