Thanks again, Trent.
The deployment process you mention is how I do
it. That's why I really don't need to manage the report by another
process. It's
probably just as easy to provide it with a new front
end.
--- In
[email protected],
Trent Johnsey <
[EMAIL PROTECTED]...>
wrote:
> The other option is to create a reports only mdb and an
interface
mdb file.
> Folks could stay in the interface mdb file
without issue, but they
could come
> and go from the reports
mdb. Access 97 used to allow changes on
the fly, so
>
modifying reports would be no big deal while folks were in the mdb
file.
> Access 2000/newer won't allow that.
>
> I have also seen
a deploy process, where each time an mdb file is
opened, it
> checks
a network based mdb file to see what version is the latest
version.
If
> the network version is newer than the version on the desktop, then
the program
> automatically copies out the new mdb file in it's
place.
> TJ
>
> --- jmw95823 <
[EMAIL PROTECTED]...> wrote:
>
> >
Thank you for the information on the mda, Trent. I was thinking
>
> that there
> > might be a linkage to reports like there is with
tables, but
> > apparently that may not be the case.
> > I
think it's probably just as easy to release a new front end
now
>
> that I think about it. I have it set up so the user doesn't
really
> > notice. They always get the latest version when
they log on.
> > Jim
> > --- In
[email protected],
Trent Johnsey
<
[EMAIL PROTECTED]...>
>
> wrote:
> > > I have seen a setup where a company has an
Access app that
uses
> > a .mda file as
> > > a
reference. Each custom report resides in this mda file.
This
> > allows the
> > > company the ability to upgrade the
application front end
without
> > messing with
> > >
client specific data. Each report has a default in the
standard
> > application
> > > file, but the code calls the .mda
file before going using the
> > application
> > >
default.
> > >
> > > However, no report
adjustments could be made to the mda file
while
> > the
main
> > > application file is in use as the file is locked.
If you are
> > referencing temp
> > > tables in the
primary application, then the installation must
be
> >
standard
> > > throughout the organization so the mda file knows
where to
expect
> > the primary
> > > application to
reside.
> > > TJ
> > >
> > > --- jmw95823
<
[EMAIL PROTECTED]...> wrote:
> > >
> > > > Is there any downside of keeping/maintaining a report
in the
> > backend?
> > > > I would like to release a
new version of the front-end
possibly
> > before
> >
> > the report is ready. If any changes are needed on the
report, I
> > won't
> > > > have to release
another front-end. It isn't a big deal to
give
> > them a
> > > > new front end. I can do it either way.
>
> > > If I do place it in the backend, do I link it the same way
as
> > linking
> > > > a table?
> >
> > Thanks for any opinions. Jim
