[AccessD] Re: Help with Error accessing file

Steve,

I do not know why no one else caught this.  The database is corrupt.  That 
is one of the errors you get when it is.

Robert

At 12:15 PM 4/6/2004 -0500, you wrote:
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steven W. Erbach
>Sent: Monday, April 05, 2004 10:33 AM
>To: Access Developers discussion and problem solving
>Subject: [AccessD] A2K: Help with Error accessing file
>
>Dear Group,
>
>I have an Access 2000 FE/BE application loaded on a client's system in
>another city 90 miles away. I've been working with their network guy over
>the phone and he's sent me screen shots of error messages along the way.
>Here's the situation.
>
>The "master" MDB FE database is loaded on the server. I have the local
>people there create an MDE and place it in another folder so that's it's
>available for the users who download it to their workstations when a new
>version is ready. While working with my client's network guy, Bob, the MDE
>file SEEMS to be created all right; but once the compacting is finished and
>the FE starts up, the first form opens and he gets this message (it's an "i"
>message):
>
>The expression On Load you entered as the event property setting produced
>the following error: Error accessing file. Network connection may have been
>lost.
>
>   * The expression may not result in the name of a macro, the name of a
>user-defined function, or [Event Procedure].
>   * There may have been an error evaluating the function, event, or macro.
>
>When he clicks OK the startup form (which is supposed to be hidden) is there
>on the screen and the application has halted.
>
>INVESTIGATION:
>
>1) They don't have the Documentor installed so I can't see what the path is
>to the BE.
>
>2) However, I do have a form (that I cobbed from Steve Nyberg) that shows
>all the links with their paths. When we attempt to open this form we get the
>message you see above. Click OK on the message and Nyberg's SeeLinks form
>opens but with nothing showing up regarding linked tables.
>
>3) I can open the linked tables from the "master" front end. But when I open
>the table that contains the latest version number (part of the version
>upgrade system) I see something odd. This Versions table has one row. The
>table has a Default value of the Now() function in the VersionDate column.
>On my system when I look at the table I see the first row all right and in
>the 2nd (empty) row I see (AutoNumber) in the key field and today's date and
>time in the VersionDate column. On my client's system he sees #Name? in the
>VersionDate column in an empty row. He cannot add information in a new row
>because Access doesn't like the default value. So I had Bob remove the
>default value. I still get the main problem.
>
>4) The users can still run the application from their workstations using the
>old version of the FE. There hasn't been any problem there.
>
>5) The Startup form of the FE calls Carl Tribble's Auto-Linker to check the
>link status of the first table before the main switchboard menu appears.
>This is all working properly on the users' workstations.
>
>6) I tried Compact and Repair on both the BE and the FE. No change in basic
>error.
>
>7) I checked the references. They're all there.
>
>8) Only thing I haven't done (at least that I know how to do) is a
>/decompile on the "master" FE on the server.
>
>I'm sorry about the length of this message. I somehow doubt that I would
>find the problem even if I were sitting at the workstation. Bob is very
>capable, so I'm sure he's relaying to me everything that he sees.
>
>At least my clients can still work with the older version of the app. I am
>just stumped why this error message appears in the "master" front end
>database. Any thoughts, other than "Well, why the heck do you let the user
>make an MDE in the first place, ya numbskull?!"
>
>Regards,
>
>Steve Erbach
>Scientific Marketing
>Neenah, WI
>920-969-0504