In the Internet Service Manager on the web server, right click the web site and click Properties.... Then click the Unload button. The next user to hit the site should refresh all the Application objects. If it doesn't work you might have to stop and start the web service itself.
HTH
>My system is a Foxpro administration application connected to an Access table connected to an internet users side.
>
>Someone else developed the ASP page I'm working on. He puts some data in the application object. He said the reason he did this was to minimize the transfer of data that wouldn't change often. But now the problem that's happening is that someone on the Foxpro side has added a new method of procurement but it's not showing up in the dropdown list (which is part of the application object if I'm reading right -- I know it has something to do with it).
>
>So what's happening is that my computer is "remembering" the previous list of procurement methods instead of going back out to the database to find out if that's still valid. So, my question is... is there anyway to force the timeout of the application object so that it will have to go look at the database again?
>
>Thanks!
"It is an important and popular fact that things are not always what they seem. For instance, on the planet Earth, man had always assumed that he was more intelligent than dolphins because he had achieved so much -- the wheel, New York, wars and so on -- whilst all the dolphins had ever done was muck about in the water having a good time. But conversely, the dolphins had always believed that they were far more intelligent than man -- for precisely the same reasons." - Douglas Adams
