Guss Ginsburg
guss at beechnutconsulting.com
Tue Jan 22 08:47:45 CST 2013
I have seen error messages like this before, and I can usually fix them by compacting/repairing the databases. Usually it is a problem with the back-end, as it is shared between multiple users and conflicts can occur that can corrupt the database. Compact the back end first, then try and see if it is fixed. Then, if needed, compact the front end. There might also be some corrupted records in the backend that you may need to delete or deal with after compacting. Sincerely yours, Guss Ginsburg Beechnut Consulting Services Phone: 504-252-9131 Cell: 713-553-6298 www.beechnutconsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins Sent: Monday, January 21, 2013 6:47 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Access on Sharepoint He says they're all on 2010. I told him to check the dao references to make sure the acedb library is checked and to unchecked the old one -- haven't heard back from him yet. I'm probably not boing to be able to help this guy, unfortunately. Susan going. > Are they all using the same Access version on the FE? > > On 20 Jan 2013 at 18:08, Susan Harkins wrote: > >> Problem was around before SharePoint and he's getting an unrecognized >> database format error when he opens the front end. >> >> Susan H. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com