Access 2000 Runtime, Office 2003/2007, Snapshot Viewer

Hi Terri,

If you copy your ocx to a different location, you can try manually registering the snapview.ocx file using regsvr32.exe. Easiest way to do this is go to Start/Run then type

regsvr32.exe "Path to snapshot viewer OCX"

Kathy

Hi Kathy.

There are no such thing as dumb questions   Funny, as a trainer, I say that all the time...:) 

1. What o/s is your application being installed on?  XP SP3
2. Does your application use the snapshot viewer ocx, the snapshot viewer exe or both? ocx
3. What location does your application install to?  The runtime is installed to C:\Program Files\Microsoft Office\ART
4. How many versions of msaccess.exe are installed on these machines?  Office 2007 (SP2) + 2000RT
5. Do you know if there are any differences between working vs non-working machines as far as programs/updates installed?  To create the most level playing field possible, we removed the 2000RT and ran the standard corporate "push down" of XP, Office and other application updates.
6. Do the working or non-working machines have the latest security update applied for snapshot viewer? I had no success with this -- sorry, I don't remember the exact message, but it was something like "SR-1 was already applied."  I just tried running the patch on a system that is working (with Office 2003 +2000RT), and got the message "The expected version of the product was not found on your system." Also re-intstalling Snapshot separately does not help.  In most cases, running a repair on Office fixes it.

BTW -- just to vent: the only reason I am using the snapshot ocx is because it is a requirement in my application that reports display "Page [Page] of [Pages]" (not negotiable), but the report writer cannot be trusted to correctly calculate [Pages] when conditional grouping is used -- an issue I understand still is a problem in 2007.  As a kludge, I output to a temporary snapshot file, use the ocx control to open the snp and tell me thereal total page count, and re-run the report passing that number in.  If there is a better way to get an accurate total page count, please let me know!!!

7. You could try using the Windows CleanUp Utility to allow you to do a fresh install of your 2000 application.  I will look into that.

---

I downloaded a newer Snapshot Viewer but that didn't help.  It's obvious that accessing this control is the problem...  if I copy the ocx to my application folder, is there a way to "manually" register it -- would this stop Installer from thinking something else is needed?

Thanks.

===

4/1/2010 - update

Kathy, I now have another user with Windows 7 and Office 2007 who is using an earlier version of my app which does not reference the ocx directly.  Everything was working fine until they used the standard Access menu function to Send Email with a Snapshot format report -- Windows Installer immediately popped up along with the infamous 1309 error.  The app then completely stopped running.  He could not immediately get an IT staff person to run a repair on Office - so I can't say if that will resolve the issue.  W had to re-install the runtime and app to get it going again and the user will be avoiding Snapshot until further notice...

Thanks for replying Kathy,

The errors indicate missing files:

Error 1309.  Error reading from file: C:\Program Files\Microsoft Office\ART\System\MSRECR40.dll

Error 1309.  Error reading from file: ...ART\PFiles\Common\MSShared\VBA\VBA6\1033\VBE6INTL.dll

on and on and on...

Thanks Terri.

Just guessing here, but since Office apps are ideally supposed to be installed earliest version first, I'm wondering if the issue is that you're trying to install a 2000 version product on a machine that already has 2007 on it. This could be causing issues with your library files. Do you have any machines where you can install your Access 2000 runtime first and then install Office 2007?

Another option, since Access runtime is now a free download, have you tried installing the 2007 runtime for your app instead of 2000 runtime? The Access 2007 runtime can be used for both MDB (2000, 2002, 2003) and ACCDB (2007) files.

Access 2007 Download: Access Runtime

http://www.microsoft.com/downloads/details.aspx?familyid=D9AE78D9-9DC6-4B38-9FA6-2C745A175AED&displaylang=en

I'll do some researching on the 1309 error in our internal database and see what I can find...

Thanks,

Kathy

Hi Terri,

Would you be able to provide the full text of some of the error messages you have been seeing?

Thanks,

Kathy