hi Colin,

>Jim
>
>Can I pick your brains? Question are a bit basic but this is new to me and could be a breakthrough with the type of work I do.

You can try... :-)

>Can my app sit on the Snapserver - lets say its network drive letter is G - so that my workstations can do g:\myapp?

Yes, indeed.

>Are there any additional file locking / record locking issues I need to think about?

None that you wouldn't consider if you were running against Windows NT Server - basically, design as if the Snap was NT and you should be fine. See all the docs they provide - http://www.snapappliance.com/page.cfm?name=snapserverCompatibility_Microsoft&nav=support gives the basics specs for use in a Microsoft environment. See http://www.snapappliance.com/page.cfm?name=snapserverNetworkList&nav=support for other environments. These are very flexible devices.

>What downsides have you experienced? I took a quick look at the site and there seemed to be a few issues surrounding seeing ss through network neighbourhood.

None. Network Neighborhood always seems to be a problem in some environments. In a mixed 95/98/NT case, setting the most capable station as a Master Browser and disabling the rest has solved this for me in the past. In a NT domain with WINS, they work fine, though I only have put one in such so YMMV. I can't speak for 2000/XP. I think I can safely say that if browsing works good in your present network, the Snap should be readily available without fuss.

If you have a pointer to the document discussing the browsing problem, please let me see it.

>Thanks

You're welcome.