One question: Why do you get from paticipating in the VFP forum on the UT.

I'm not trying to be disrepectful, but I'm just curious.


>I have not created COM components with VFP SP3 and I don't plan on starting anytime soon. For the time being, most of our data is in FoxPro Databases, but that will soon change. Our company has grown from 300 million to over 800 million dollars in sales in only 5 years. As we buy more and more canned software packages(Foxpro doesn't do everything), we have been forced to install both MS SQL Server and Oracle. We also have 3 AS400's and applications that don't use any data at all. Our plan is to use SQL Server for our Web backend. Myself and everyone else in the MIS Dept. agrees that VB is going to be our best bet for an all around good development language.
>
>If anyone has any better ideas why we should stick with VFP.....I don't want to hear them.
>
>This is my one and only experience with VFP Components:
>
>When I updated a previously installed VFP Component(VFP 6.0 without SP3) in MTS, I was not able to access any other MTS packages due to an error being generated from the only VFP component on my machine. I had to reinstall NT Option Pack and re-create all of my MTS packages to correct the problem. I have been using VB to create my Com Components for a year and a half and I have never had any problems out of them.
>
>This is my preference. Please don't start sending me replys with "VB Sucks/FoxPro Rules" messages.
>
>>Tim,
>>
>>I'm curious: have you been able to work with any VFP COM components created with VFP 6 with SP3 applied? If not, I think your opinion might change a little.
>>
>>I'd like to hear about your bad experiences as well, if you have the time to describe them.
>>
>>>I disagree with you, I don't think VFP is a Tool to be used to develop internet/intranet sites/apps. VFP COM objects do not integrate well with MTS, yet. I have had nothing but bad experiences with VFP COM Components with MTS. VB Components are more robust(In my opinion).
>>
>>Regards,