Re: An Interesting Occurance w/Access 2003



On Wed, 13 Feb 2008 03:32:35 GMT, Donald Calloway
<drcalloway@xxxxxxxxxxx> wrote:

You may have been bitten by Name Autocorrect:
http://allenbrowne.com/bug-03.html

-Tom.


I have an application with a number of tables, one of which I named,
Calls, which holds information relating to telephone calls. Anyway,
making a copy of the database file, then making a number of
modifications to it, I deleted all of the records in the Calls table of
the modified database, renamed the table to Calls2, and then proceeded
to copy and paste the Calls table from the original database to the
upgraded database. Of course, the upgraded database now contains two
tables of the same design: A blank Calls2 table and a Calls table, a
copy of the table from the original database containing all of the
original data. There is a data entry form in the original database
which uses the Calls table as the record source. Naturally, the
upgraded database also contains the form which uses the Calls table as
the record source. When I opened the upgraded database, I received an
error whenever I clicked on a switchboard option which opens the data
entry form in edit mode. A microsoft error dialog box said the form's
record source could not be located or accessed. This occurred, mind
you, even though the record source property of the form was the Calls
table, and there is a table by the name of Calls in the database. I
scratched my head and wondered, why doesn't the form recognize the
blasted Calls table since the table is right there in the database?
Anyway, what I tried and and it worked was, I had to go to the form's
properties, click on the record source property combo box and select
another table as the record source temporarily, then reselect the Calls
table as the form's record source. Somehow, the Calls table had to be
reestablished as the form's record source after the copy and paste was
done even though the names were identical. Has anyone else ever come
across this before?
.



Relevant Pages

  • Re: Corrupt Form
    ... always work on a copy of the database. ... make it impossible for a repair service to fix it. ... The Record Source of my form is a SQL table. ... All the other forms in the mdb remain connected to ...
    (microsoft.public.access.forms)
  • Re: Unbound form
    ... I am working with a Access 97 Database. ... trouble of unbounding some of the forms in the database is because when the ... Allen Browne - Microsoft MVP. ... record source is set when the form is loaded and cleared when the form is ...
    (microsoft.public.access.formscoding)
  • Re: An Interesting Occurance w/Access 2003
    ... of the modified database, renamed the table to Calls2, and then ... database to the upgraded database. ... which uses the Calls table as the record source. ... switchboard option which opens the data entry form in edit mode. ...
    (comp.databases.ms-access)
  • An Interesting Occurance w/Access 2003
    ... Anyway, making a copy of the database file, then making a number of modifications to it, I deleted all of the records in the Calls table of the modified database, renamed the table to Calls2, and then proceeded to copy and paste the Calls table from the original database to the upgraded database. ... the upgraded database also contains the form which uses the Calls table as the record source. ... When I opened the upgraded database, I received an error whenever I clicked on a switchboard option which opens the data entry form in edit mode. ...
    (comp.databases.ms-access)
  • Re: An Interesting Occurance w/Access 2003
    ... of the modified database, renamed the table to Calls2, and then ... database to the upgraded database. ... which uses the Calls table as the record source. ... switchboard option which opens the data entry form in edit mode. ...
    (comp.databases.ms-access)