If you are workin through the web environment to access your site and modify files, the "everyone" users group must have either change or full control to the folder or the file.<BR><BR>At least from my experiences.<BR><BR>-- Whol
are you using that code you posted yesterday about the application variable to prevent a refresh in any "live" web site??<BR><BR>cause if you IMO there are bugs in it and that is definitely not even close to fool proof
Actually it was one of my attempts to have an ACCURATE PAGE HITS<BR>counter.I got that idea and i think when i last wrote, it was working fine.(i just tested before posting here, not an extensive test).But i would definitely like to know about the BUGS/Shortcomings of it.
I did not post yesterday cause did nto think you would read it<BR><BR>For starters you are not locking the application at all<BR><BR><BR>but more importantly let us say you have page A calling B and page C also calling B.<BR><BR><BR>Now when i navigate from page a to b it is one hit and if i refresh it would work fine...now another user navigates from page c to page b and another hit...now what will happen if *I* refresh the page...let me tell you.....ANOTHER hit...see that...the application variable has changed SO it will be another hit for me...<BR><BR>As long you can navigate to that page from ONLY one link it will work fine OR if there is only ONE user at a time.<BR><BR>Now if you store the total hits in the db then you could use a session variable to do what you are doing and i would not see any bugs like this. but that will be hitting the db on each page....sucks huh.<BR><BR>Thinking about it now i am not sure if there is really a method that would definitely work right...hmmmm maybe we could think of something else.<BR><BR>