Front End/Back End Dilema

[kermit5]

I have created a database with the tables in a back end database and the queries, forms, reports etc. in a front end database. In my front end, I linked the tables to the back end.

Now when I send both the front end and the back end to the client, an error appears because the linked tables are in folders of different names.

I seem to be missing a componant of the front end/back end concept. Is there a way to package the two databases together so the client can put the two of them (together in the same folder) anywhere on his/her system and still maintain the linked tables?

Thanks in advance!
Scott

 

[Autoeng]

The easiest way to get what you need is to recreate the clients directory structure on your machine. For instance the client will put the FE in C:\My Documents and the BE in C:\Directory Name?. Make that same setup on your pc. Move the files accordingly. Open the FE. Using Tool-Database Utilities-Linked Table Manager relink the tables. Place a check mark by all the table names and put a check mark in the little box at the lower left hand corner that says "Always prompt for new location". Select the OK button. The rest of the process is self explainatory. (Note that these instructions are for Acess 2000 and above). If you are working in A97 use help to locate the Linked Table Manager. I know it's under the Tools menu but not sure where).

Now copy the FE and BE to disk and send to client. Make sure they set up exacly as you. They should be good to go. Now If they plan on locating the BE on a server you've got a problem as you can't recreate their server during the link process. You will need to code in a utility that prompts them to point to the new location of the BE. I think you can find an example at wwww.rogersaccesslibrary.com under the downloads section.

 

[Autoeng]

I post too fast before reading the entire question. Since the client is putting the FE and BE in the same directory you will do same but with the same directory names. Same as I posted before but ignore the different directory example.

 

[kermit5]

If I am going to distribute the databases to multiple clients, am I better off keeping everything in a single database?

 

[Autoeng]

Yes.

 

[pat_nospam]

I'm looking at this same exact situation -- Pat, can I get a copy of the link you mention below.

Thanks again,

Pat

I would leave the db split. You can attempt to relink the db behind the scenes. You can determine the directory of the current db and assume that the path to the be will be the same or you can open the common file dialog box for the user to "find" the be for you. Or, you could combine the two. First try to find the tables and if that fails, prompt. If you search the archives you should find code. You can start with the example in the solutions database. If you don't have that, I have also posted links to it.