Re: Newbie to Access Developer Extension
From: Albert D. Kallal (PleaseNOOOsPAMMkallal_at_msn.com)
Date: 08/02/04
- Next message: Sirocco: "Office 2003 Developer"
- Previous message: Albert D. Kallal: "Re: Is This How It Works?"
- In reply to: Nancy: "Newbie to Access Developer Extension"
- Next in thread: Sirocco: "Re: Newbie to Access Developer Extension"
- Reply: Sirocco: "Re: Newbie to Access Developer Extension"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 2 Aug 2004 16:29:16 -0600
"Nancy" <ncdocken.nospam@msn.com> wrote in message
news:9b8101c478c1$bd8c0d30$a501280a@phx.gbl...
> I will be attempting to publish a very simple Access
> application as a runtime, and need some advice as to
> whether I'm heading in the right direction.
>
> I'm doing a contract gig at a good-size corporation. They
> need to have a form available to people who use a shared
> drive, whether they have Access on their computers or
> not.
The use of the term shared drive is likely a bad term. The concept of shared
drives goes back to my university days when they where hauling out the
punched card machines. As a general rule, you do NOT want to rely on drive
mapping. People have little jump drives (those little USB things with
memory), portable cd players and all kinds of memory card readers. When you
plug in one of those devices, then all the drive letters can change.
So we all know that drive letters can vary, then it follows that to reduce
support calls, then YOUR software should NOT rely on drive letters. You want
to use UNC path names at all times. That is:
\\serverNamae\YourCoolApplicatonDir\MyBackEndata.mdb
>
> Anyway, I've built a two-form database that feeds tables
> in another database (that only contains the tables) that
> will be used by a group that actually has Access on their
> computers, along with other forms and reports to use to
> slice and dice the information entered by the form-only
> users.
You should be aware that the runtime system is in fact a full blown version
of ms-access. The ONLY difference is that the runtime version does not let
users flip into design mode..but other then that...the run runtime system is
in fact a full blown version of ms-access. (and, like most companies, you
will need admin privileges to get that system installed...and I would have
to guess that MOST users do NOT have admin privileges). In other words, you
still are in fact installing ms-access on each computer, and the proper
channels in that company to get a large software package installed must be
followed.
>
> The two-form database consists of a switchboard where the
> first time user prints instructions on how to get
> permission to use the form, and a space where they can
> enter their password and reach the main form after
> permission has been granted.
So, I assume that you are using ms-access security to accomplish this? How
are passwords being granted to users here?
> Am I leading them astray by suggesting they put the two-
> form database on their shared server for all to use as
> needed, and use the data gathered to get the answers they
> need with the more robust Access database?
You don't mention how many desktops, and how many users you expect. If there
was only going to be one, or two max users at the same time, them you COULD
get away allowing multiple users into the front end. However, if you are
talking about multi-users in the 3-20 range, then you most certainly MUST
put the mde front end on each pc (...you use a mde for all your
users...right?).
Remember, that ms-access is different then word, or excel that is ms-access
is a software development tool. I mean, you always purchased software and
placed it on EACH computer. You put word on each computer. You put Excel on
each computer. Fact is, if you make software with ms-access, then once
again, you put the application on each computer (you done this for
years..and just because YOU make the software, this does not change the fact
that you put the software on each computer). of course, you can share word
docs on the server. Of course, you can share excel data on the server. And,
of course, you can put the DATA ONLY part of ms-access on the server also.
But, in ALL CASES you put the SOFTWARE on each computer. No one is
suggesting that you try and install Excel on the server, and have every one
use it. The same applies to your software also.
Also, is the corporate network a lan, or wan? You can read about wans, and
lans and deploying ms-access in a corporate network here:
http://www.attcanada.net/~kallal.msn/Wan/Wans.html
And, in addtion to that tip about using UNC path names, here is 10 more
quick tips for you:
http://www.mvps.org/access/tencommandments.htm
-- Albert D. Kallal (Access MVP) Edmonton, Alberta Canada pleaseNOOSpamKallal@msn.com http://www.attcanada.net/~kallal.msn
- Next message: Sirocco: "Office 2003 Developer"
- Previous message: Albert D. Kallal: "Re: Is This How It Works?"
- In reply to: Nancy: "Newbie to Access Developer Extension"
- Next in thread: Sirocco: "Re: Newbie to Access Developer Extension"
- Reply: Sirocco: "Re: Newbie to Access Developer Extension"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
