Access 2003 keeps confusing form names

[AnandaSim]

Hi All,

I'm experiencing what I think is a bug - can't figure out how it would
be stated so difficult to search the NG.

I have a form. It has four listboxes. Each listbox has a rowsource. The
four listboxes cascade in criteria. So the next listbox in the sequence
uses the formname!listboxX as the criteria for the rowsource. Not
unusual.

Now comes the odd part. As I edit the rowsource - using the query
designer UI but keeping it as an SQL string, when I'm ready, I run the
Form. But the SQL strings now reference some other Formname, not the
current formname. So I thought it was me and I edit them and save and
run. Reverts again. Finally, I don't use SQL string, I save each
rowsource as a query and use a queryname as an SQL string. Happens
again - the formname changes somehow.

Tried Repair and Compact.

Seen that?

[tina]

i'm guessing that you didn't turn OFF the Name Autocorrect option when you
created your database (for more information, see
http://home.att.net/~california.db/tips.html#aTip3).

suggest you create a new, blank database. immediately turn OFF the Name
Autocorrect option - from the database window's menu bar, Tools | Options |
General tab. compact the database. import all the objects from your current
database into the new one. fix the SQL strings in the form in the new
database, then compact the database.

if you still have problems, suggest you try the above again, but do *not*
import the "problem" form. instead, after importing all other objects and
compacting, rebuild that form from scratch.

hth
"AnandaSim" <An*******@gmail.comwrote in message
news:11**********************@b28g2000cwb.googlegr oups.com...

Hi All,

I'm experiencing what I think is a bug - can't figure out how it would
be stated so difficult to search the NG.

I have a form. It has four listboxes. Each listbox has a rowsource. The
four listboxes cascade in criteria. So the next listbox in the sequence
uses the formname!listboxX as the criteria for the rowsource. Not
unusual.

Now comes the odd part. As I edit the rowsource - using the query
designer UI but keeping it as an SQL string, when I'm ready, I run the
Form. But the SQL strings now reference some other Formname, not the
current formname. So I thought it was me and I edit them and save and
run. Reverts again. Finally, I don't use SQL string, I save each
rowsource as a query and use a queryname as an SQL string. Happens
again - the formname changes somehow.

Tried Repair and Compact.

Seen that?

[AnandaSim]

Thanks for that. I guessed as much and have turned it off in the
current db. But not gone the whole way of exporting everything to a new
mdb.

I've been on access 2000, 2002, 2003 for a long while but this is the
first time it has given me so much trouble.

Ananda

tina wrote:

i'm guessing that you didn't turn OFF the Name Autocorrect option when you
created your database (for more information, see
http://home.att.net/~california.db/tips.html#aTip3).

suggest you create a new, blank database. immediately turn OFF the Name
Autocorrect option - from the database window's menu bar, Tools | Options |
General tab. compact the database. import all the objects from your current
database into the new one. fix the SQL strings in the form in the new
database, then compact the database.

if you still have problems, suggest you try the above again, but do *not*
import the "problem" form. instead, after importing all other objects and
compacting, rebuild that form from scratch.

hth
"AnandaSim" <An*******@gmail.comwrote in message
news:11**********************@b28g2000cwb.googlegr oups.com...

Hi All,

I'm experiencing what I think is a bug - can't figure out how it would
be stated so difficult to search the NG.

I have a form. It has four listboxes. Each listbox has a rowsource. The
four listboxes cascade in criteria. So the next listbox in the sequence
uses the formname!listboxX as the criteria for the rowsource. Not
unusual.

Now comes the odd part. As I edit the rowsource - using the query
designer UI but keeping it as an SQL string, when I'm ready, I run the
Form. But the SQL strings now reference some other Formname, not the
current formname. So I thought it was me and I edit them and save and
run. Reverts again. Finally, I don't use SQL string, I save each
rowsource as a query and use a queryname as an SQL string. Happens
again - the formname changes somehow.

Tried Repair and Compact.

Seen that?

[tina]

once you start building objects in a database, Name Autocorrect can continue
to haunt you even after you go back and turn it off. i don't know why, but
it can be a real PITA; so if i forget to turn it off immediately, i just
stop in my tracks and go the "new db, import objects" route as soon as i
realize my oversight - i find it quicker and easier in the long run than
holding my breath and waiting to see if a problem occurs. :)

"AnandaSim" <An*******@gmail.comwrote in message
news:11**********************@i42g2000cwa.googlegr oups.com...

Thanks for that. I guessed as much and have turned it off in the
current db. But not gone the whole way of exporting everything to a new
mdb.

I've been on access 2000, 2002, 2003 for a long while but this is the
first time it has given me so much trouble.

Ananda

tina wrote:

i'm guessing that you didn't turn OFF the Name Autocorrect option when

you

created your database (for more information, see
http://home.att.net/~california.db/tips.html#aTip3).

suggest you create a new, blank database. immediately turn OFF the Name
Autocorrect option - from the database window's menu bar, Tools |

Options |

General tab. compact the database. import all the objects from your

current

database into the new one. fix the SQL strings in the form in the new
database, then compact the database.

if you still have problems, suggest you try the above again, but do

*not*

import the "problem" form. instead, after importing all other objects

and

compacting, rebuild that form from scratch.

hth
"AnandaSim" <An*******@gmail.comwrote in message
news:11**********************@b28g2000cwb.googlegr oups.com...

Hi All,
>
I'm experiencing what I think is a bug - can't figure out how it would
be stated so difficult to search the NG.
>
I have a form. It has four listboxes. Each listbox has a rowsource.

The

four listboxes cascade in criteria. So the next listbox in the

sequence

uses the formname!listboxX as the criteria for the rowsource. Not
unusual.
>
Now comes the odd part. As I edit the rowsource - using the query
designer UI but keeping it as an SQL string, when I'm ready, I run the
Form. But the SQL strings now reference some other Formname, not the
current formname. So I thought it was me and I edit them and save and
run. Reverts again. Finally, I don't use SQL string, I save each
rowsource as a query and use a queryname as an SQL string. Happens
again - the formname changes somehow.
>
Tried Repair and Compact.
>
Seen that?
>