>Quick question... Is all data in SQL-Server...???

No, currently the data warehouse is held in a VFP 6 database.

>Also, you scenario sounds backwards. Typically, production/transaction databases update data warehouses...not the other way around... Please clarify this...

An off the shelf app uses SQL server for its data source. The reason it sounds backwards is:

Although the SQL Server data can be updated by the off the shelf package, it isn't. The users are just looking up and querying data out of it.

The Data warehouse is maintained by a VFP 6 app that remotely logs into over 30 Novell servers and collects legacy data in a variety of formats. It then "normalizes" the data and stores it in a VFP database. This is one area where if it makes sense we could be warehousing the data on SQL Server instead, but the collection and maintenance will be handled programattically by VFP. The warehouse is updated daily, with most of its work handled between 11:00pm and 7:00am when network traffic is ligther (on a private WAN). The warehouse *should* contain the most up to date information that the off the shelf product needs. Make sense?

>
>IAC, if you need the power of VFP Cursors, then I would suggest using SPT and stored procedures to actually perform the updates....

Yeah this is what I'm seeing, SPT is more powerful, Remote Views are more familiar to me, but then again I relish jumping into something I've not done before!