Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2001-05-02 : 14:21:02
|
Todd writes "I ran into this and was stumped for a while with no answer in site. I searched everywhere with not one answer to be found I went to figure it out myself. I know the answer now but I saw your site (neat name) and I thought I would share but your guru probably already has the answer probably. Ok here it is!
I ran into this problem on a NT server with a site that was using cold fusion. The site was using access (but it could have been SQL it don't matter) as a database that the site referenced to often for listings. The site received many visitors a day this is important to the problem. The problem was the client was not able to update the listings in the database unless he was lucky enough to get to the database when noone was on the site in the database in other words he could not do updates (which he did daily) to the database and upload it to overwrite or anything unless noone was browsing his domain. The problem was a security token set on the domain much like on your pc when you open a database file by microsoft it sets a little security token next to it in the same file. Question is for the guru: How to fix the database on the server so that the security token does not interfer with updates so you could overwrite the database on a domain when the database is open??
Just asking, Todd" |
|
|
|
|