Yes Cathy, I couldn't agree more, it should - but alas, it don't. (Yes I know, bad grammar <g>). I don't think it has anything to do with remote views though, since I experienced the same behaviour with the following:

USE MyRemoteView
* Get a structure extended into MyArray
Create Cursor Temp FROM Array MyArray 
USE DBF('Temp') ALIAS MyCursor again IN 0
SELECT MyRemoteView
SCAN
   SCATTER MEMVAR
   INSERT INTO ....
ENDSCAN

And I guess that's as local as it gets?

I've pinned it down to VFP 8.0 SP1, and I assume it's a plain old bug.

I had a number of reports which were created in VFP 7.0. The app was ported to VFP 8.0 and everything worked fine, reports with remote views and all.

This report I'm having trouble with, was designed in VFP 8.0, and it just won't run. Of the 49 records in the view it would print four, like 1, 17, 33 and 49, all rather randomly.

So I decided to try a novel approach - that is, to try to create a report against the same view with VFP7.

Lo and behold, it worked, and, what's better still, it now also runs under VFP 8 without a glitch.

Another thing I found, was equally strange:

In VFP8 run the report wizard, pick your table(s) or view and all the other stuff, save it and then try to edit it. I get a dialog asking would I like to port this OLD report format to a newer version, say yes, get told that there is nothing to transport (I should say not) and that's it.

If it's created with the wizard, it's simply impossible to modify that report in VFP8.0.

Strange stuff, huh?

Finally, do you have any idea as to how the private datasession in the report designer works, and how one can get a report to run in a private datasession, 'cause I sure as .... can't seem to get it to work.

BR

Peter

>I'm not aware of any problems. You can open the remote view just prior to running the report. Just be sure the report is *NOT* defined with a private data session, otherwise, it won't be able to see the view that was opened prior to running the report.
>
>Another option is to open it in the data environment of the report.
>
>Either way should work just fine.
>
>Cathy
>
>
>
>>In a very simple, no frills-report based on a remote view, a REPORT FORM...
>>command prints only 4 of 50 records.
>>
>>The only thing I know, that's different from similar reports is, that the datasource is a remote view.
>>
>>Are the issues that I'm unaware of?
>>
>>If so, please enlighten me.
>>
>>TIA
>>
>>Peter