Changing BE table name/subsequent error

[RosieMP]

Please help, folks -- I need advice. I'm horrified to have found after splitting a database and rolling out the fe/be that a table is named incorrectly. When a user tries to launch a particular query (that produces a report) they get a 3078 error because a table is not found. Evidently at some point in development I'd decided a table wasn't going to be used, stupidly, it turns out, and changed its name to tablename DELETE (I offer no excuse for this.)

I changed the tablename back to the table name that the query calls, but I'm still getting the error when the button is pressed and the query tries to launch--it's still saying the table name is incorrect, although I can see that the table name matches the table name in query.

I've never split a database or used a fe/be before and I'm not skilled at the administration.

Can someone offer some advice?

Thank you!

 

[RosieMP]

Okay, I think I figured this out, so for anyone who finds themselves in a panic this is what I did:

I changed the be table name to what I wanted, then deleted the link in the front end, then I readded the table link in the front end.

It didn't seem to be enough to just change the name in the backend, and then change the name in the front end.

 

[JerryKlmns]

RosieMP

The name of a linked table is something for the FE to talk to. If you open the (hidden) MSysObjects table you'll see that for every linked table (Type=6) there is besides its Name, a ForeignName! They might be the some, but they might not. Changing the linked table in the FE, you just chenge the Name and not the ForeignName. If you change the name of the table on the BE, you definetely have to relink the table. Either delete the link and create it again or use code to change that value.