I get an error that a file in the Data subdirectory of the program folder cannot be updated. I have set permissions for that subdirectory to give full rights to Everyone.

If Reporting4Act! is installed on a share on a server, set the permissions for both the share and the folder to full rights for the Everyone group.

I scheduled a report but it doesn't run. When I run it manually in the Windows Task Scheduler, I get a "This task requires that the user account has Log on as batch job rights" message.

The account you specified for the task must have permissions to run batches. On a local server, use the Local Security Policy Manager:

• Click the Windows Start button, type "secpol.msc", and press Enter

• Expand Security Settings, Local Policies, User Rights Assignment

• Double click "Log on as a batch job"

• Click the Add User or Group button and add your account

• Click OK

On a domain controller, use the Group Policy Management Editor:

• Click the Windows Start button, type "Group Policy", and click Group Policy Management

• Either edit the existing GPO that contains existing User Rights Assignment (likely Default Domain Policy) or right-click and Create and Edit a new policy

• Expand Computer Configuration, Windows Settings, Security Settings, Local Policies, User Rights Assignment

• Double-click "Log on as a batch job"

• Click the Add User or Group button and add your account

• Click OK

When I select a certain report, I get a "Report contains tables and/or fields you do not have permission to access" error and I can't print the report.

As the error message indicates, you cannot access that report because it contains at least one table or field the administrator has determined you cannot access.

I have Reporting4Act! installed on a server and published it as an application on a Terminal Server. However, when anyone runs Reporting4Act!, they get an "MSVCR71.DLL cannot be found" error.

Since Reporting4Act! is actually running on the Terminal Server (even though it's installed on the other server), you need to do at least a workstation install on the Terminal Server, because certain runtime files (such as MSVCR71.DLL) are required.

When I run a report, I get a "File c:\temp\somefile.tmp does not exist" error in the CreateReportFile method.

This error is most likely caused by having the System flag on your temporary files folder. To turn this off, click the Windows Start button, choose Run, enter ATTRIB C:\TEMP -S (in place of C:\TEMP, specify the path for your temporary files folder), and click OK.

Another possibility is that you have disk write caching turned on for your hard drive. To turn that off:

• Click the Windows Start button, type "Device", and click Device Manager in the list.

• Click the plus sign next to Disk Drives to expand it.

• Right-click the drive on which you want to disable disk write caching, and then click Properties.

• Click the Policies tab and turn off the Enable write caching on the device option. Click OK, then close the Device Manager.

When I start Reporting4Act!, I get a "bad path" or "invalid path or file name" error before anything appears.
This is caused by an invalid directory listed in your PATH environment variable. Click the Windows Start button, type "environ", and choose Edit the System Environment Variables from the list. Click the Environment Variables button and check the contents of the Path variable.

I'm getting a "Date/DateTime evaluated to an invalid value" error when I run a report.

This error occurs if you have dates in your database prior to 01/01/1601. Reporting4Act! doesn't support dates earlier than that.

I'm getting an "Unable to create temporary work files" error when I run a report.

Reporting4Act! puts some files in your Windows temporary folder. This error occurs if that folder is read-only, marked as hidden, or the volume it's on is almost full. You have to fix this problem before you can run any reports.

When I run a report, I'm getting an "invalid path or file name" error.

If you use the Advanced Report Designer to add an image to a report and you specify Expression or variable name for the Image source type setting, the field you use for the image must contain a valid image file name for every record in the report or you'll get an "invalid path or file name" error. In that case, set a filter on the report for that field not being empty.

I'm trying to schedule a report, but when I click Finish, I get an error message stating that the schedule couldn't be saved.

A scheduled report has to run under a specific Windows account, so be sure to enter the login name and password of the account to run the report under in the last step of the Schedule Wizard. Normally, this is your usual Windows user name and password. If you are on a network, you may need to specify the domain using "DOMAIN\USERNAME."

The scheduled task cannot be saved if you don't have a password for your Windows account.

I get an "insufficient GDI resources" error when I run a certain report.

This error occurs when you run a report that has more than about 4,800 pages. The issue is that Windows has a limited number of resources available for producing graphics, which is what report pages are output as. You have a few choices:

• Use a filter to limit the report to less than 4,800 pages (the exact limit depends on your system and what other applications are running).

• Output the report to PDF rather than printing or previewing it.

• Bump up the number of resources Windows provides using the Registry Editor. Edit the value of the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\GDIProcessHandleQuota key from the default of 10,000 to something higher, to a maximum of 65,536.

  This is for advanced users only who are comfortable changing the Windows Registry.

Reporting4Act! crashes when exiting.

This happens on some Windows 7 and later systems. To fix this problem, turn off the Use special Windows features setting in the Options dialog.

I am getting a "There are too many fields in this report. Please reduce the number of fields and try again" error when I run a certain report.

This happens when the SQL statement used to process the data for a report exceeds 8,000 bytes. One way to fix the problem is to remove some fields from the report, but if you really need all of the fields in the report, you can turning off the Process null values specially setting on the Data page of the Options dialog. This reduces the size of the SQL statement by eliminating null processing. That means you might not get the results you expect if any of your fields contain null values, but at least the report runs. Since this setting affects all reports, you may wish to change it just for this one report by adding the following to the BeforeData script for the report (click Advanced in step 2 of the report wizard to access that script):

loDataEngine.lHandleNull = .F.