In my continued quest to solve this problem (in desperation really), I started to erase, one by one, the memo fields found in the first record of the FRX file. For good measure, I PACKed the table after each deletion. It wasn't until I deleted the content of the FONTFACE memo field (it had "Arial" stored in it) that the problem suddenly went away. Now this report will run without generating the dreaded "Resource Manager internal consistency" error.
But since this is the only report I'm having this problem with, I'd like some confirmation from other people that this unorthodox action fixes other instances of this problem as well (and doing no apparent harm). If it can be confirmed then I think I'll clear out this field on the first record of every FRX I have.
Paul
PS: This is a VFP 3.0b and Windows 3.1 problem.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only