Phil
The front end is a good place for temporary tables, ones that hold throw-away data for reports and such. Sometimes a report is so complex that you need to run several queries to get the data to display properly. Just before the report opens you run a procedure to fill the temp table and then use that table as the report's RecordSource. Putting it in the front end lets multiple users gather different data when just a filter will not suffice. If the table was in the back end users would be competing for what data goes into that table. As you can see, that just won't work.
One thing about the SwitchboardItems table... I always make my own switchboard that does not rely on a table. That way it's easy to tailor it to groups of users by hiding or showing specific buttons through code that looks up the user's group in a table.
I don't know how skilled you are with VBA, but you might want to give something like that a shot.
Regards,
Bill Mosca, Founder - MS_Access_Professionals
http://www.thatlldoit.com
Microsoft Office Access MVP
https://mvp.support.microsoft.com/profile=C4D9F5E7-BB03-4291-B816-64270730881E
My nothing-to-do-with-Access blog
http://wrmosca.wordpress.com
---In ms_access_professionals@yahoogroups.com, <pdk444444@yahoo.co.uk> wrote:
Ahhhh - so I can have a mixture of some tables in the front (actual tables) and some in the back (links) - eg different switchboard tables held and maintained in each front end?
I just had an inkling that there was some interference between import specs in the 2 front ends ( ie I thought I had made a change in 1 front end and then saw the same change in the other front end) but I can check that out more thoroughly now you have told me that they should be held in the front ends and I know what to expect.
Thanks for the quick reply
cheers
Phil
From: John Viescas <JohnV@msn.com>
To: MS_Access_Professionals@yahoogroups.com
Sent: Friday, 22 November 2013, 14:02
Subject: RE: [MS_AccessPros] Split database
Phil-
Simply delete the link to the SwitchBoardItems table and import that back into the front end from the back end. The splitting should have left your import/export specs in the front end.
John Viescas, Author
Microsoft Access 2010 Inside Out
Microsoft Access 2007 Inside Out
Microsoft Access 2003 Inside Out
Building Microsoft Access Applications
SQL Queries for Mere Mortals
(Paris, France)
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of pdk444444@yahoo.co.uk
Sent: Friday, November 22, 2013 2:41 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Split database
Hi Guys
I know you will be amazed (and probably disgusted) that I haven't done this before but I have split a database for the first time!!!
So I now have a back end and 2 front ends and I am discovering that further development now has its challenges!
First of all I soon realised that menu changes (switchboard) were of course stored in the BE tables - so I assume I now have to provide my own menu facilities for FEs where I want to provide different functionality?
Also, I am not yet sure about saved imports and exports - to save me time experimenting - can someone tell me if the saved import and export specs are saved in the FE or the BE?
If there any other obvious pitfalls you can make me aware of I would appreciate that.
cheers
Phil
Tidak ada komentar:
Posting Komentar