Agree that "glitch" does not equal "bug." Everything I could find pointed to MSoft's desire to reduce traffic on the network, so they have a fairly short disconnect time, like 15 minutes. (Not sure of the exact time, just surmising.) I don't have any problem with that.
What does seem to be a problem is that none of the VFP commands would reconnect the dropped share. I tried the low-level command, i.e., fopen(), as well as adir() and directory()....all of them would just throw an error and the connection would remain "down" according to Windows Explorer. As soon as I clicked the share in the Windows Explorer window, VFP was happy and all requests for information from the share worked as expected. I may be paranoid about this, but I expect that someday, somehow, there will be an issue that VFP just does not handle with a new MSoft OS and the end will be in sight. Mike > Thanks Mike, could come in useful. > > On Wed, 04 May 2011 23:31 -0500, "Mike Copeland"<[email protected]> > wrote: >> Did not want to do this as the older >> server works great...except for this new Windows 7 glitch. >> >> > It might be due to the fact that the network stack in Windows 7 is very > different and has incompatibilities with the older Samba, but I wouldn't > necessarily be calling it as a bug. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
