Split out Reports from a FE into its own db???

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Rick Roberts - 14 Feb 2005 13:35 GMT

I am developing a good size app in Access 2003 with a FE / BE configuration
with most of my users using a Run Time version of Access that I will include
in my install package.

Currently all the reports and associated report forms are defined in the FE
along with everything else. My thought is to separate out the report related
items into it’s own db for purposes of maintenance. I can foresee a lot of
changes to the report db while the changes to the rest of the objects would
be minimal (hopefully!).

Do any of you MVP’s out there have a thought on this? I am just now getting
my mind around Front End Updating. I have seen Tony ‘s web site about the
Auto FE Updater and I am intrigued.

From a programming/security point of view it’s simpler to keep it all in
one, however I am interested in quicker loading, ease of maintenance and
whatever else I haven't thought of.

If I do split out the reports then what would be the best way call them from
a switchboard type menu? Application.Run? I do a lot of VBA coding so I am
not afraid to try anything!

I have a lot of thoughts swimming around my head and I would truly
appreciate anyone comments/experience with this type of issue.

Reply to this Message

Tony Toews - 16 Feb 2005 21:47 GMT

>I am developing a good size app in Access 2003 with a FE / BE configuration
>with most of my users using a Run Time version of Access that I will include
[quoted text clipped - 9 lines]
>my mind around Front End Updating. I have seen Tony s web site about the
>Auto FE Updater and I am intrigued.

My biggest app has 450 forms and 350 reports. It is about 22 mb in
size as an MDE. Updating it using the Auto FE Updater only takes a
few seconds over the network.

There is no real good reason to split things like you are proposing.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

Reply to this Message

Rick Roberts - 16 Feb 2005 22:33 GMT

Thanks Tony,

I don't have nearly that amount of forms or reports (as yet) but my MDE FE
is about 18 mb. After having spent some time on this issue I am inclined to
agree with you and leave well enough alone.

> >I am developing a good size app in Access 2003 with a FE / BE configuration
> >with most of my users using a Run Time version of Access that I will include
[quoted text clipped - 23 lines]
> Microsoft Access Links, Hints, Tips & Accounting Systems at
> http://www.granite.ab.ca/accsmstr.htm

Reply to this Message

Simon Maystre - 29 Mar 2005 20:57 GMT

I have managed to do this quite effectively with an application being used
by about 150 different companies. I needed the report file to be seperate so
that each company could have its own unique report layouts for invoices
etc... without having to update the main program file. All you need to do is
keep set a reference from your main program to the file containing the
reports and add a module in the reports with a function as below:

Public Function MMReport(ReportName, Optional ViewMode, Optional FilterName,
Optional SearchPhrase)

If IsMissing(ViewMode) Then
DoCmd.OpenReport ReportName, , , SearchPhrase
Else
DoCmd.OpenReport ReportName, acViewPreview, , SearchPhrase
End If

End Function

Then you can access all the reports as you would in a single app but use the
MMReport function. One major limitation is that you cannot use an MDE it has
to be an MDB.

Simon

>I am developing a good size app in Access 2003 with a FE / BE configuration
> with most of my users using a Run Time version of Access that I will
[quoted text clipped - 28 lines]
> I have a lot of thoughts swimming around my head and I would truly
> appreciate anyone comments/experience with this type of issue.

Reply to this Message