[AccessD] Fw: Problem with Access

Jim:

That might have worked.  Actually, I just got a call from him and the solution turned out to be registering DAO 3.51 using regsrvr32 but he was told that the DLL had to be in the same folder where regsrvr32 was.  So that's what he did and now it's working.

Thanks everybody for the feedback.

Rocky

  ----- Original Message ----- 
  From: Jim Dettman 
  To: accessd at databaseadvisors.com 
  Sent: Thursday, June 19, 2003 12:55 PM
  Subject: RE: [AccessD] Fw: Problem with Access


  Rocky,

    Well they can go through a quick re-install of A97 using SETUP/y, which will force a re-write of the registry keys no matter what, but it really sounds like an environment problem.  My guess is that the references are broken.  However the error message is typical of a coding problem.  The message indicates that a process is trying to be killed, but it's already exited, meaning it some type of timing issue.

    I'd start by checking the reference and refreshing.  Then re-install if the /y switch if that still doesn't do it.
  Jim Dettman
  President,
  Online Computer Services of WNY, Inc.
  (315) 699-3443
  jimdettman at earthlink.net 

    -----Original Message-----
    From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Rocky Smolin - Beach Access Software
    Sent: Thursday, June 19, 2003 11:45 AM
    To: AccessD at databaseadvisors.com
    Subject: [AccessD] Fw: Problem with Access


    Dear list:

    Does anyone know the answer to this one?

    MTIA,

    Rocky Smolin
    Beach Access Software

    ----- Original Message ----- 
    From: Dave McDonald 
    To: Rocky Smolin 
    Sent: Thursday, June 19, 2003 6:54 AM
    Subject: Problem with Access


    Rocky,

    The question that you have to ask your users group is:

    What is necessary to do to eliminate the message "<process has already exited>has generated errors and will be closed by Windows.  You will need to restart the program."  This message is probably due to previous installations of ACCESS97 which were not completely removed from the registry and subsequent installations of Access97 do not correct this.  

    The problem occurs only when running (or trying to run) ezmrp.mdb or ezmrp-ro-locked.mde.  Other databases open normally.

    The problem is in this machine since this machine cannot open any ezmrp.mdb on any other machine and other machines can open the ezmrp.mdb on this machine.

    Thanks,

    Dave


------------------------------------------------------------------------------


  _______________________________________________
  AccessD mailing list
  AccessD at databaseadvisors.com
  http://databaseadvisors.com/mailman/listinfo/accessd
  Website: http://www.databaseadvisors.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030619/4a78d17f/attachment-0001.html>