On Thu, Oct 23, 2008 at 9:00 AM, Richard Kaye <[EMAIL PROTECTED]> wrote: > Interesting idea. You've given me some food for thought.
Unfortunately, I think I answered the wrong question. I thought the situation was that the controlling application and the slideshow were on the same machine. COM Automation would be a good answer for that one. When they are on different machines, you need to look at DCOM, which is very rarely the right answer: Microsoft's solutions to networked solutions are often far more difficult and unstable than alternatives. Intimate and persistent connections between machines over a network doesn't have a lot of good solutions in the VFP frame. In this case, I'd be more inclined to look back towards your original design, passing data throug a VFP database. Check your REFRESH settings, or caching: that's likely why Machine B doesn't see Machine A's changes for a second or more. The other question I'd have is why use VFP as a slideshow presenter. While VFP is the finest datktop database management and rich database client ever created (but look out for Dabo!), this doesn't seem like a database problem. Why not a browser front end with a Javascript refresh, reading a directory or a VFP/IIS application? -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: ProFox@leafe.com 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.
