Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Front-End/Back-end

Status
Not open for further replies.

gtree

Programmer
Aug 8, 2002
11
US
Question regarding using Access as both the Back-end and front-end in a multi-user environment.
I have split my Database.
My FE is still retaining data. I don't want data in the FE. How can data be stored ONLY in the BE?
I was reading some answers given earlier on this website,
It said "3) If your FE still has data tables, import them into the BE file and link them from the BE to the FE. You may choose to leave some lookup tables in the FE for the sake of speed but this is not necessary"
I imported the tables from the FE back to BE and deleted them from the FE. Now when I try to open the Form on my FE it says MS Jet Database engine cannot find the input table or query. Also there are now 2 sets of tables in my BE

How do you think I should go about creating a BE-FE in a multi-user environment using Access. the FE would be Access Forms/Reports.

If you could please answer this, it would help me a lot.

Thanks

 
Hiya,

Quick and simple:

I'm not going into FE / BE benefits etc.

You want a front-end application using a back-end database.
First back your application up elsewhere - just in case.

(A)
You've got your total application.
Copy it to where you want your data to reside.
In it's new location - leave it as it is or delete all objects (forms, queries, macros etc EXCEPT the tables).

(B)
You've got your total application.
Copy it to where you want your 'front-end' is to reside.
Delete the tables.
Within this application without tables: create new LINKS.
When asked what you want to link to - find the tables from the location of the application in (A) above.
(To create a 'LINK' - goto tables - click 'NEW' and you will be given a 'LINK' option')

This is the simplest way of telling you how to create a FE/BE system.

Regards,

Darrylle






"Never argue with an idiot, he'll bring you down to his level - then beat you with experience."
 
Hi Darrylles,

Thanks a ton.
Just a quick one on the linking part. How do I link the tables in the front-end if the back-end is on a separate machine (server)? Do I have to map the drives on my client to be able to link? Any other alternatives??
 
You do have to map the drives on the users machines - I am not aware of any alternatives.

Fred
 
No. No. Do not use a Mapped Drive (though it will work). Use a UNC address path to the server. I have customers that have no standard mapping so "S" on one machine is "G" on another. As Microsoft says (this time they are actually correct):

"Important If you link to a file on a local area network, make to use a universal naming convention (UNC) path, instead of relying on the drive letter of a mapped network drive in Windows Explorer. A drive letter can vary on a computer or may not always be defined, whereas a UNC path is a reliable and consistent way for Microsoft Access to locate the data source that contains the linked table. "
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top