>Then, you'll easily be able to change your data access class to use web data instead of local data.
>
>

oData = CREATEOBJECT('customerdata')
>oData.OpenCustomerTable()
>
>oForm = CREATEOBJECT('form')
>oForm.AddObject('oGrid', 'grid')
>oForm.oGrid.RecordSource = 'customer'
>oForm.oGrid.Visible = .T.
>oForm.Show(1)
>
>DEFINE CLASS customerdata AS Custom
>	PROCEDURE OpenCustomerTable
>	LOCAL oDataXML, lcXML
>	oDataXML = CREATEOBJECT('customerdataxml')
>	lcXML = oDataXML.OpenCustomerTable()
>	XMLTOCURSOR(lcXML, 'customer')
>	ENDPROC
>ENDDEFINE
>
>
>* Open up the customer table and return it in XML format
>DEFINE CLASS customerdataXML AS Session OLEPUBLIC
>	PROCEDURE OpenCustomerTable
>	LOCAL lcXML
>	USE HOME(2) + 'Tastrade\Data\customer.dbf'
>	CURSORTOXML('customer', 'lcXML')
>	RETURN lcXML
>	ENDPROC
>ENDDEFINE

>


Forgive this really dumb question ... but

how does the above coding change allow one to access web data instead of local data.

Ultimately you open the customer table with the command

USE HOME(2) + 'Tastrade\Data\Customer.dbf'

isnt that local?

could you clarify what
"Session OLEPUBLIC" means... ?

are building a .dll that sits on a machine at the different IP address and then 'SERVES' the data via XML ?

If indeed accessing web data between two machines is this simple...
I'm buying VFP 7 tomorrow.