[AccessD] Error # 3343 Unrecognized database format

Colby, John JColby at dispec.com
Fri Jan 30 12:56:36 CST 2004


>Hopefully they won't automatically back up their corrupted database...

lol.  You can bet on it!

John W. Colby
The database guy


-----Original Message-----
From: Rocky Smolin - Beach Access Software [mailto:bchacc at san.rr.com]
Sent: Friday, January 30, 2004 1:40 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Error # 3343 Unrecognized database format


Hopefully they won't automatically back up their corrupted database...

Rocky

----- Original Message ----- 
From: "Doug Murphy" <dw-murphy at cox.net>
To: "'Access Developers discussion and problem solving'"
<accessd at databaseadvisors.com>
Sent: Friday, January 30, 2004 10:21 AM
Subject: RE: [AccessD] Error # 3343 Unrecognized database format


> Thanks Greg and Rocky,
>
> I visited the customer and found that the problem, while still
> unaceptable, is something that happens infrequently.  When  I got the
> call it sounded like it was happening every time they used the DB.
> Fortunately every time they close the system down it backs itself up.
> The network they use has just kind of grown so there are lots of places
> network errors could be introduced.  The good thing is they will be
> upgrading their network soon so hopefully this will be a thing of the
> past.
>
> Doug
>
> Douglas Murphy
> Murphy's Creativity
> (619) 334-5121
> doug at murphyscreativity.com
> www.murphyscreativity.com
>
>
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Greg Smith
> Sent: Thursday, January 29, 2004 6:21 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Error # 3343 Unrecognized database format
>
>
> Doug:
>
> I've seen this before.  One of my clients has A97 FE and BE and
> occasionally gets the "Unrecognized db ... error".  Their MIS guy has
> found that almost every time it happened they had a bad switch, bad NIC,
> or bad wiring which was causing the user's FE to break the connection
> improperly, leaving the BE in a questionable state.  Of course, the same
> thing can occur if users reboot their computers or reset them without
> logging out of Access first.
>
> HTH!
>
> Greg Smith
> weeden1949 at hotmail.com
>
>
> ----- Original Message ----- 
> From: "Doug Murphy" <doug at murphyscreativity.com>
> To: "'Access Developers discussion and problem solving'"
> <accessd at databaseadvisors.com>
> Sent: Wednesday, January 28, 2004 5:44 PM
> Subject: [AccessD] Error # 3343 Unrecognized database format
>
>
> Folks,
>
> I have a client who has started getting an Error #3343 on their back end
> DB.  The DB is Access 97. From what I can find on this error it usually
> has to do with database writes being interupted or hard shutdowns.  They
> claim that there have been no changes to thier network and that all etc.
> etc. _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


More information about the AccessD mailing list