Recently Microsoft have introduced a patch that blocks the access of compiled HTML help files across a network. Network access to such files was considered a security issue by Microsoft. Is there any other format in which the help files can be compiled and accessed from a visual FoxPro application.
Rick,Ramani and Dave
Thank you all for your help, the problem is now solved. The Fatal Exception error is caused by the HP 41000 Laserjet print driver. The solution is to set up an additional printer "Generic / Text Only" and then in the code use the following sequence suggested by Rick when...
I have installed a genric text only printer as an additional printer and when this is selected as the default then there problem goes away. However the problem is switching backwards and forwards between printers when you want to print a report as compared to saving it as an ASCII text file...
Dave
The file names are generated automatically using a fixed string plus a string conversion of the date and time. I have been having the same problem on two different machines. I will do as you suggest and tidy the hard disks.
Thanks
Dave
Dave
Yes, I have sufficient rights because the files are only being written to C:\Temp directory. The problem was at first intermittant but has become more frequent as I have tried to address it.
Thanks
Dave
Rick
My test machine is set up with an an HP 4100 Laserjet as its default printer.
My application is a standalone executable developed using Visual Foxpro v7 service pack 1. The operating system of my test machine is Windows 2000.
The application is running on the same machine as the...
When printing to an ASCII text file I get a Fatal Exception error C00000005. I have tried removing any printer information from the frx file by clearing the TAG, TAG2 and EXP memo fields but this makes no difference.
The error does not occur when printing to the default printer.
I am trying to use an automated testing tool called Test Complete from AutomatedQA with a Visual FoxPro 7 application. The testing tool can see forms and controls within them in the uncompiled version but not in the compiled executable. I suspect that this is because it cannot utilise the...
I have used HTML Help Workshop and FronPage to build a compiled help system (.chm) for my application. The system works fine on my development machine (Called either using the F1 key or from a menu option). However, when I place it on a machine which does not have Foxpro the help file cannot be...
Can anyone explain the reason for the following events. I have a formset containing 3 forms layered one on top of another. Each form is linked to a view and the views are linked in a grandmother, mother, daughter one to many relationship. Each form has two buttons [New/Save] and [Close/Cancel]...
For Mike Lewis
Mike
I tested your suggestion of using
THISFORM.dataenvironment.cursor1.database = "MyDBC"
in the load event of the form. Unfortunately this produces an error. Looking through the help files this is expected. Help indicates that you should use the Open and Close...
Is there a way of setting the data environment for a form programmatically rather than using the data environment GUI. I want to use a view as the cursor source for a form but be able to specify the database location which holds the view. I cannot see a way to set these programatically since...
FoxPro version 7.0
I have tried installing Service Pack 1 but this had no effect on the NT machine. I am not aware of any later service packs.
There was a similar error fixed in service pack 1 which occurred with CREATEOBJECT() when you programmtically call Microsoft Visual SourceSafe. I am not...
Has anyone experienced the above error when using the following code constructions
THISFORM.methodname(
THISFORMSET.methodname(
I have been using these code constructions when attempting to set up code within a form or formset that will allow the passing of parameters to a method of...
Can the colour of individual rows in a visual Foxpro 7.0 listbox be set. I would like to colour some rows different to others based on values within the row source table.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.