Form's underlying table name changes

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi all!
This is a general question about forms and a test/production environment.

I could not get the "General" area to open so I could post to it there. I
apologize if this is in the wrong area.

I need to know how to handle table name changes, after a form or application
is built.
My task is to build a small application (for reporting purposes) in a test
envronment.
I can build my queries and forms, based on existing tables in a specific
directory in TEST.
However, then the client then wants the application moved to "Production".
In Production, the table names start with a different prefix.

I know I can go in and re-link tables, but how will this affect everything
else that I build? Will it automatically pick up the new table names? And
will it automatically do this for my queries and forms?
 
No, it will not pick up the new table names. You will have to change them
once you move the app to production. You are creating (or having created for
you) a nightmare. If at all possible, make the table names in both databases
the same. Changing a table name will confuse every form, report, query, or
macro based on that table.
 
Thanks, Klatuu, for your quick response!

I was afraid that might be the only answer to this. However, due to naming
conventions for these tables, test and production have different prefixes.
I will take it up with the programmer handling the table creation.
 
I have worked in environments in the past were names have changed:
tables, fields, etc. This can be a nightmare. Imagine a major Access
application with a multitude of forms/reports/queries/modules... One
name change can have a major impact. Unfortunately, sometimes this
does happen.

I attended an intermediate Access programming class in the mid 90's
taught by Rick Fisher (http://www.rickworld.com/). Among other things,
he mentioned two products that can help when renaming can't be avoided:
Speed Ferret and his Find & Replace. Initially, I purchased SF and it
was good. I decided to purchase his add-in (only $37) and try it. In
my opinion, Rick's product does far more that SF and is at least $130
cheaper. I have continued to use his product when necessary and it has
never failed me. No, I am not on his payroll or any contact with him,
just a programmer who looks for efficient ways to do things....

Bob
 
Thank you Klatuu, for your quick response.
This is my 4th attempt at replying to your answer. The other 2 errored out,
but may show up anyway.

I was afraid that was the only answer for this.
The test/production naming conventions are set in stone.

I will take it up with the programmer that is creating the tables.
 
Got your response, G. Also saw the response from bob. I have used both of
the products he mentions. Speed Ferett is not up to date. It is only good
through 2000. If you have > 2K, you have to have a 2K verison installed to
use it. Rick's tool is good, but I have not purchased the upgrade. It seems
to work well. It would be useful in your situation because you could do a
find and replace on each name that changed from test to production, but that
is extra work.
I think discussing this with the programmer and explaining to him the
problem with changing a name in an Access environment would be your best
solution.

Good Luck
 
If you cannot get the table names the same there is a possible work-around.
When you link Access to the test tables, rename the links to the names of the
live tables. You can then build your FE with all of the names in place for
when you relink to live.

HTH
John
 
Back
Top