Hello Gang,
I've just created a "Data Aware Form Class", based on an idea I gleaned/plagiarised, from Jim Booths' book "Effective Techniques for Application Development with Visual Foxpro 6.0". [Great Class - Great Book]. Basically the classes' Load event, strips the forms' DE Cursor objects ( saving the properties to arrays etc... ), and rebuilds them using its' own Cursor classes. Using these classes with data on the local hard disk works fine, but it appears ( on a network ) that if you issue This.DataEnvironment.CloseTables(), rebuild the Cursor(s), and then issue This.DataEnvironment.OpenTables(), the Exclusive property of the Cursor class (which defaults to .t. for local views ), tries to open the underlying tables exclusivley, and results in a "File Access Denied" error message if run on a network. Is this a bug or am I missing something?, I've checked all the obvious exclusive settings to no avail ( I'm not using Private Data Sessions ). My workaround is to set the Exclusive property to .f. in my base Cursor class, but I would like to get to the root cause of this, the VFP help says that the Exclusive property always affects the underlying tables when used with local views, if so why does it work when you add views to the DE visually, any ideas?

Regards

Pete Kane