Re: A2K on 2003 Server

Not sure why the particular combination is causing it to fault, but you
desperately need to apply some service packs to your Office 2002.

You may also need service packs for JET:
http://support.microsoft.com/kb/239114

Once you have both those sorted out, open the front end (holding down Shift
to bypass any opening form/code/macro), and choose:
Tools | Database Utilities | Compact/Repair
The front end caches info relating to the attached tables. That info will be
wrong after your upgrade. Compacting the front end causes Access to drop
that cached info, and can prevent crashes.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"BruceS" <bruce \at\ springthorpe.org> wrote in message
news:5E50A70C-227C-48E5-9FB2-C0B31F548168@xxxxxxxxxxxxxxxx
For the super techies...

We just upgraded our NT server to 2003. After the upgrade, we moved an
A2K
database that updates records in a back end to the server and set it up in
Scheduler to run with a command parameter. The backend resides on the
same
physical computer and drive as the .mdb. The program had been working
fine
on a WinXP Pro workstation (also using a command parameter) with local
copies
of the backend databases.

Since installing on the new server, about every 4th or 5th time the
application tries to run, it throws the following error:

Application failure msaccess.exe 10.0.2627.1 at offset 0x0000a8f3

When you view the details, you see the following:

Exception information:
Code: 0x00000b20
Flags: 0x00000000
Record: 0x00000000c0000005
Address: 0x00000000

On most occasions, but not all, this results in a lock file for the front
end.

To try to find out what was going on, we put extensive error trapping and
logging into the front end .mdb. Nothing shows up, not even in the
Form_Open
of the form that is automatically opened when the app starts. We've run
the
program on the XP Pro development machine at least one hundred times
trying
to get it to fail. Nada, nothing. It works perfectly.

The problem appears to be compatibility issues with 2003 Server. Has
anyone
heard of anything like this going on?

Any input/help deeply appreciated.

Thanks,
Bruce


.

Relevant Pages

  • Re: Upgrade from MSDE to SQL
    ... Hard to say whether the database is of any use to you now you are partway ... upgrade just in case. ... But FIRST I would in any case see if adding SQL Server ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Using Access 2000 w/FP2003 w/XP Home Edition
    ... FTP it to their server? ... >> database to integrate into a web page and get errors. ... In addition, IIS (Internet Information ... do I need to upgrade my PC from ...
    (microsoft.public.frontpage.programming)
  • Re: Using Access 2000 w/FP2003 w/XP Home Edition
    ... your web site on the server. ... >>> database to integrate into a web page and get errors. ... > Programming Interfaces), ... do I need to upgrade my PC from ...
    (microsoft.public.frontpage.programming)
  • Re: URGENT: Hotfix 941422 on WSS 3.0 causes WSS to fail
    ... SQL Server instance 'DBSERVER' is not empty and does not match current ... Please upgrade this SharePoint application server before ... The schema version of the database WSS_Content on ... I am having the exact same issues running the new WSS Service Pack ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: WSS 2.0 to 3.0 upgrade
    ... The first upgrade I did I also did an in-place and nothing good came from ... time it took for the database to attach. ... Windows 2003 server, the SQL Server, restoring from backup to WSS 2.0, ...
    (microsoft.public.sharepoint.windowsservices)
Loading