>I have finally upgraded to 5.0a. After having to uninstall and reinstall in order to get this to work I thought I was on my merry way.
>
>But...an application that I have written has a form that uses 2 mscomm ActiveX controls for talking to 2 serial ports. After having upgraded I made some minor changes to the application--nothing to do with the ActiveX controls or that particular form. I created a setup routine using the setup wizard after recompiling and installed this on the machine that had been running the app without any problems for some time.
>
>Now...the app seemed to run fine but the communications with both serial ports were hosed. They would communicate but not properly. I figured the machine had gone south considering it was an old 486 and had them buy a new one.
>
>What do you know...it still doesn't work on a brand new machine that has never held this app nor VFP. I ended up installing VFP 5.0a on that machine as a last ditch effort. Now it works.
>
>So...my question is: Does anyone know what files I need to replace on a client machine to work? Or why a recompile and a new setup does not include the correct files?
>
>TIA,
>George

I've had a sort of similar experience in going to 5.0a. It seems that the ActiveX treeview control cannot get it's .ImageList property to be set anymore.
I just have a hard time accepting that a bogus control was shipped with an upgrade.

Steve