Hello Wim,

so now we meet on the UT after our conversation in Amsterdam. Good to see that you are an active member of this community.

Thanks for your tip but it is not the solution to my problem. I assumed that the problem had to be -view- related and I therefor decided not to requery the view but to requery the database with the sql-statement of the view into a cursor. This immediately solved my problem but it still makes me wonder why this happened in the first place.

A big bonus is that by redesigning the program with sql has improved the performance and also made it multi-user stable whih it wasn't with the views.

The report that I have designed is too complex for any report-writer (including VFP's). It contains so many 1-many relations ships and an enourmous number of fields (>200). FPW26 was streched to its physical limits. VFP, however, doesn't know how to deal with the same report. There is a serious bug in the report writer with left and right column alignment. It orginated in VFP3 and it has not yet been solved.

This report has been created with Virtual Print Engine (www.idealsoftware.com). In fact, it is not a report but a program that writes to the print engine. Thinking outside the box can be challenging. If you are using MS-Word for reporting you should take a close look to VPE. It is a engine, trully controleable and extremely fast. It really knows how to handle RTF (unlike MS-Word). My report took > 2 minutes to be created with MS-Word, it now takes 10 seconds with VPE. Making such progress really impresses customers....

Thanks,

Ron Brahma