Vin,

You’re right I am not blaming the ISP. MS is entirely to blame for VFP’s poor perception and lack of support. What wound me up was my conversation with a support staff that told me "Access is a better database for Web development than FoxPro." When I asked him where he heard that he said "One of our MCSEs."

What really pisses me off is when MS says we should upgrade to support VFP when MS itself is the ONLY reason the product has such a small market to begin with.

>Will -- I agree with what I think you are saying -- that any anger or frustration should be geared toward Microsoft and not the ISP. From the ISP's pov, I can understand this decision. There are only a very small percentage of customers requesting software XYZ, and Microsoft has never really pushed it as a legitimate technology. Of course they would want to research the product pretty thoroughly, under those circumstances, before loading it. And, at a certain point, doing so is not cost-effective.
>
>I'm certainly not defending MS, but I would defend the right of an ISP to reject support for a given technology under some circumstances. And, as we know, Microsoft has never exactly made life easier for Foxpro developers by promoting the product...
>
>
>>Jaime,
>>
>>No problem leaving the ISP... Just pointing out yet another negative effect of Microsoft's stepchild treatment of VFP. An ISP that trouts itself as a Microsoft technology shop that does not support a Microsoft product listed with all the other supported products at http://msdn.microsoft.com/vstudio/. I don't see Access in that list.
>>
>>>Will
>>>I don't see what is your problem with leaving the ISP? You can find here on the UT a list of very good ISP's that even support VFP apps ( ie. not only the odbc drivers... ). In your place, i would move everything to one of the new ISPs, have all my clients move with me, and explain clearly to the guys at uplinkearth.com that the lack of VFP support is what made me move.
>>>
>>>Jaime
>>>
>>>>Anyone run into problems using VFP data on an ISP http://www.uplinkearth.com/ server? I am doing some volunteer ASP.NET development using a VFP database. Planned on moving the SQL Server soon but not now.
>>>>
>>>>How do I convince a full-blown Microsoft ISP shop to support a Microsoft product? Should VFP be so shamed by Microsoft in the eyes of their customers that they don't even acknowledge Visual FoxPro as a Microsoft product? Does this seem ridiculous for such a mature, high-performance product?
>>>>
>>>>Could someone from Microsoft please tell me why this is? Can anyone?
>>>>
>>>>Better yet... Can someone at Microsoft tell http://www.uplinkearth.com/ that Visual FoxPro is a Microsoft product and a very good one at that. Is this too much to ask? I mean what the f... is going on in Remond Washington?
>>>>
>>>>---Support Follow-up---
>>>>Will,
>>>>
>>>>We'll have to have network look into this as it is something we usually
>>>>do not support.
>>>>
>>>>--
>>>>Arturo Hernandez
>>>>Customer Service Representative
>>>>
>>>>
>>>>--
>>>>
>>>>> ---Original Message---
>>>>> Hello Support,
>>>>> I get the same message again when writing to the VFP database.
>>>>> The error is :
>>>>> Microsoft OLE DB Provider for ODBC Drivers error '80004005'
>>>>> [Microsoft][ODBC Visual FoxPro Driver]Cannot update the cursor.
>>>>> It was fixed on the 9th of March. I copied the message below.
>>>>> Thank you,
>>>>> Will
>>>>> ---Support Follow-up---
>>>>> Will,
>>>>> We do have the lastest drivers from MIcrosoft. However, FoxPro is not
>>>>> one of our officially supported databases. The FoxPro driver runs
>>>>under
>>>>> the "IWAM_" account which we don't ususally set up permissions for. I
>>>>> have added the permission and verified access (you can ignore the
>>>>> request from me). You should have no further problems. For future
>>>>> reference, if you need to use FoxPro on another site, please annotate
>>>>> the ticket with reference, "I using a FoxPro database and this
>>>>requires
>>>>> special handling".
>>>>> If we can be of further assistance, please open a new support ticket.
>>>>> --
>>>>> Byron Adams
>>>>> Customer Support