[Ray62]

QUOTE(Author #2 @ Jan 19 2006, 11:15 PM)

Ray62,

You must have something typed into each C# field in each row.? If it is blank on the report, put whatever the nearest C# value is above that.? Then your error will go away.

Author #2

[snapback]2097[/snapback]

Does the same thing apply for the other fields as well.

I have records that have nothing in the RCVD-DT, ASSIGN-TO and CAT columns.

Do I put the nearest value for these records as well?

Ray

[Ray62]

Thanks for the link Author #2. I tried that one first and it worked right away even with the networked printer. It must have been a corrupted database file.

Ray

[Ray62]

After further review of the issue and the updates (microsoft operating system and office), I have to ask if anyone has this working with msjet40.dll with the following version.

4.0.9025.0 Update Rollup 1 for Windows 2000 SP4

This one does not get overlayed even with service pack 8 of the MS Jet 4.0 drivers which loads the following.

4.0.8015.0 Service Pack 8 (SP8)

But under the knowledge base from Microsoft, this is the recommended process to take to correct this error. It does not say what to do it the version you have is higher than the latest service pack for MS Jet 4.0 drivers.

It can be found here –> http://support.microsoft.com/kb/239114/

Any thoughts?

The above version looks to have gotten loaded from my service pack 4 update.

Ray

QUOTE(Ray62 @ Nov 1 2005, 11:26 AM)

The environment:

Windows 2000 Service Pack 4 with all the latest updates.

Office 2000 Service Pack 3 with the latest updates.

Pentium 4 running at 2Ghz

512MB RAM

The issue:

After adding myself as a User on the Users form.

I go to the FOIA Generator form.

Put in the date the FOIA request (I01), the service center and click on the certified copies. When I click print, I get “MSACCESS.EXE has generated errors and will be closed by Windows. You will need to restart the program. An errorlog is being create.”

I then switched to a machine that never had Office and loaded Office from scratch and then the updates to the OS and then Office and then got the same error with the MFDecoder when I attempted to print.

I noticed a post for an updated Secured.mdw file which I tried as well and I still get the same error.

Let me know if I am missing something or doing something incorrectly.

Thanks,

Ray62

[snapback]1921[/snapback]