Russ
- I think you are right about the terminology, but it would be best if we got clarification from the Beave.
We developers commonly call Access databases with forms and reports "Applications".
Bill Mosca.
--- In MS_Access_Professionals@yahoogroups.com, "ghsclass65" <dyspoz2@...> wrote:
>
> I don't mean to put words in the Beaver's mouth, but he's probably calling Access applications "programs". Obviously in Access you can have a bare bones db with no forms, buttons, reports, etc. But in my mind, when you start adding things that make it simple for the non Access developer end user, it becomes an application or I guess you could call it a 'program" if you wanted to.
>
> Russ
>
> --- In MS_Access_Professionals@yahoogroups.com, "Clive" <zctek@> wrote:
> >
> > Hi Jerry,
> >
> > It is not clear to me what you mean by "programs".
> >
> > Are they Macros, VBA Subs and Functions in Modules,
> > complete .mdb files, or something completely different?
> >
> > If you like you can upload a sample to the Group Files
> > 2_AssistanceNeeded folder, nothing confidential and
> > suitably zipped.
> >
> > Regards, Clive.
> >
> > --- In MS_Access_Professionals@yahoogroups.com, Duane Hookom <duanehookom@> wrote:
> > >
> > > Every Access application should be split into front-end and back-end files. All of your changes are typically made to the designs in the front-end queries, reports, forms, code, etc. The back-end contains only tables.
> > >
> > > There should be code in the front-end that checks for the location of the back-end and possibly allows users to link to a back-end in a different location.
> > >
> > > Sending updates should be a no-brainer. They simply open the new front-end and are connected or prompted to their back-end.
> > >
> > > If you need to make changes in the back-end table structures, this can be handled with some DAO or other code.
> > >
> > > Duane Hookom MVP
> > > MS Access
> > >
> > > ----------------------------------------
> > > > From: jerrymathersasthebeav@
> > > >
> > > > I've created a few Access "programs" that others have found useful so I've given them a copy of the most recent version. Of course, it seems like a program is never done and I continue to make minor adjustments and tweaks to the program (okay, occasionally there may be a need for a major change due to an error I found/created). These mostly consist of some relatively minor changes to a Query or two and/or a Report. I might even need to add a new Query and Report, as well. The problem is I need to get any changes I've made in my copy into the copy I gave them.
> > > >
> > > > These people aren't working in my building. They are all working at other schools and are less familiar with Access than even I am so explaining how to make the changes isn't a viable solution. What I have been doing is asking them to let me have temporary remote access to the location where they are storing their copy of the file. Then I make the changes or add the new Query and Report by hand. This is okay, but what I'd really like to do is find a way to send them some kind of "package" containing all of the changes that will automatically update their copy of the program (without touching the data they've already input). I cannot think of any way to do this, but the thought occurred to me when I was doing some basic updating of various programs on my computer that there are so many programs that have automatic update capability it gave me the idea of doing something similar with their copy of the Access file.
> > > >
> > > > I was wondering if anyone can offer some suggestions on how I might manage this problem through an "automatic" update process for Access files. How to do you get any updates into your client's files? Have you figured out some way other than by hand?
> > > >
> > > > Any ideas would be greatly appreciated!
> > >
> >
>
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (5) |
Tidak ada komentar:
Posting Komentar