John
Thanks for the confirmation.
Bill
--- In MS_Access_Professionals@yahoogroups.com, John Viescas <JohnV@...> wrote:
>
> Bill & Darwin-
>
>
>
> That particular problem has been reported before - as far back as 2003. It
> indicates some sort of corruption in the database.
>
>
>
> http://www.access-programmers.co.uk/forums/showthread.php?t=76523
>
>
>
> I would also suspect Name AutoCorrect if it's turned on. Make sure it's turned
> off, then create a new database and import all the objects from the old one.
>
>
>
> John Viescas, author
> Microsoft Office Access 2010 Inside Out
> Microsoft Office Access 2007 Inside Out
> Building Microsoft Access Applications
> Microsoft Office Access 2003 Inside Out
> SQL Queries for Mere Mortals
> <http://www.viescas.com/> http://www.viescas.com/
>
> (Paris, France)
>
>
>
>
>
>
>
> From: MS_Access_Professionals@yahoogroups.com
> [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Bill Mosca
> Sent: Sunday, July 01, 2012 9:43 PM
> To: MS_Access_Professionals@yahoogroups.com
> Subject: RE: [MS_AccessPros] Primary Key
>
>
>
>
>
> Darwin
>
> I've never had that happen to a 2003 back end (or front end for that matter). Do
> you have the latest Office updates installed? The unpatched version of 2010 was
> a bit buggy. Even SP1 had its problems so the latest updates are essential.
>
> Regards,
> Bill Mosca,
> Founder, MS_Access_Professionals
> That'll do IT <http://thatlldoit.com/> http://thatlldoit.com
> MS Access MVP
> <https://mvp.support.microsoft.com/profile/Bill.Mosca>
> https://mvp.support.microsoft.com/profile/Bill.Mosca
>
> From: MS_Access_Professionals@yahoogroups.com
> <mailto:MS_Access_Professionals%40yahoogroups.com>
> [mailto:MS_Access_Professionals@yahoogroups.com
> <mailto:MS_Access_Professionals%40yahoogroups.com> ] On Behalf Of Darwin
> Sent: Saturday, June 30, 2012 7:23 PM
> To: MS_Access_Professionals@yahoogroups.com
> <mailto:MS_Access_Professionals%40yahoogroups.com>
> Subject: [MS_AccessPros] Primary Key
>
> I just had a problem that I have never had before. One of my tables changed the
> Primary Key field, that is it remove the property. This cause 5 of my forms to
> not accept data. As soon as I made the field a Primary Key again everything
> worked fine. I am using Access 2010, but the tables (that is the backend) were
> created in Access 2003. Has this happened to anyone else? And what could cause
> such a thing to happen?
> Thanks,
> Darwin
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
Tidak ada komentar:
Posting Komentar