Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
General fields for Word Documents
Message
From
28/04/2006 19:46:10
 
 
To
All
General information
Forum:
Visual FoxPro
Category:
Reports & Report designer
Title:
General fields for Word Documents
Environment versions
Visual FoxPro:
VFP 9 SP1
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01117729
Message ID:
01117729
Views:
47
I have about 500 users on our software which focuses on documents produced from vfp reports. These reports have comment sections (perhaps a 2" x 7" area on the page.) Our users type their comments in a Word document saved on the harddrive. When printing the vfp report, I determine by changing the margins of the Word document to see if it will fit into the alloted space in my vfp report. If it doesn't fit I just print the Word document as a whole on the side. Otherwise I append the Word doc to a general field in a temp table which my frx looks at (using a ole bound field). This has worked for years and continues to when run in the vfp8 version of our software. We have been making the transition to vfp9 making changes in our code with queries, etc. I've slowing been putting people on the vfp9 version of our software. Although most of my customers on the vfp9 version of our software are working fine with the above code, I now have 2 cases (and fear there might be more if I put more on it) where these general fields are not showing on the report at all (when the report is run with vfp9 object assisted mode) yet they show when doing it the classic way (when people send our documents to PDF I'm still using the classic way because the pdf document appears chopping when done with object assisted mode).

I also use xfrx in our software to export the report to word. When people export our reports to Word, I'm using the objected assisted mode since xfrx works so much better and faster in that mode. I notice that these 2 cases when exporting to word the area where the word comment would go show complete black (I'm not saying xfrx has a problem, just saying what it looks like when exported with their code.)

Does anybody have any idea what may be going on here? Or perhaps a better solution? At one time in the past, Norton's script blocking always threw an iviewobject error when our software was trying to print one of these documents. But one of the customers having this problem doesn't have antivirus software on there at all (a very isolated computer/sever) so I don't feel like that has anything to do with it.

Sean Gowens
Anchor Commercial Services
Reply
Map
View

Click here to load this message in the networking platform