Re: Access database

"Gwen" <Gwen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:99DAC8BA-BE3B-40C8-AB86-884869D3724B@xxxxxxxxxxxxxxxx
A I mentioned before, the number of work stations where a front end would
be
required is many. It would not be feasible to manually visit each station
to
install a front end. It would need to be a global install which I think
would
require IT involvment.

Actually, have them read my article. here:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

At the end of the day, they installed word on each computer. At the end of
the day, they install excel on each computer. in fact, likely for the last
20+ years they installed EVERY application on EACH computer. Now your
telling me that you built an application, but you NOT going to install it on
every computer like you done with ALL OTHER software? You don't think this
is a strange attitude on the IT department? It sounds like the IT department
does NOT know the difference between a document like word, and that of
application that you or your developers built.

since every other software application is installed on EACH computer, then
why not yours?

You mean if ONE person in the building has a problem with Excel, then you
want EVERYONE in the building to have the same problem?

You have to think about his......

You can roll your own update system in a hour or two, or simply using one
like tony's free updater here:

http://www.granite.ab.ca/access/autofe.htm

There is ABSOLUTE no excuse for this type of development process in which
everyone other software your have gets installed on EACH computer, but then
you then simply diss out this idea for YOUR software? Why would your
software be treated different when word, or excel, or simply accounting
software?

It like your in a form for cars and you telling me that you don't believe in
changing the oil in the car...but then are asking why your having problems?
If one user has a problem in the front end...then others users can suffer
the same damage if they all are in the same front end. Why would you risk
your reputation and stability of your work and do things different then how
all other software is run on those computers? If you have too many problems,
it very likely your put your job and reputation at stake in which they
replace you because your application is not performing well. Keep in mind
just like a bad car that you don't trust for a trip you are about to take,
your users will feel the same way about your software. Once they loose
confidence in your application, it hard to get it back and have users trust
your system. You need to do EVERYTHING to ensure that your stuff runs
well. If your software has too many problems then users will perceive
this lack of performance. Your users will think what you have is kind of ok,
but is 2nd rate quality. You don't want to give your users the idea that
your application needs to be replaced with something more professional and
robust.

I not trying to sound hard here on you, I am just trying to give you the
"sense" that there are consequences not doing things right and this can
be a FAR greater cost then just some egg on your face...but in fact can
jeopardize your whole work and efforts.

I **want** you to succeed in your efforts.

--

Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@xxxxxxx



.

Relevant Pages

  • Re: Experience with 2003 & 2007 on same computer?
    ... each version of Excel uses its own set of registry keys. ... To find the correct path, open XL 2003, open VBA, CTRL G to ... Even if you install just Excel, ...
    (microsoft.public.excel.misc)
  • Re: Experience with 2003 & 2007 on same computer?
    ... each version of Excel uses its own set of registry keys. ... To find the correct path, open XL 2003, open VBA, CTRL G to ... 2007 if I install only Excel 2007? ...
    (microsoft.public.excel.misc)
  • Re: Excel 2003 + 2007 on dev machine - deployment problems on Excel 2003 machine
    ... I then started developing my application, and realised when I came to the Excel part that most people would be using Office 2003. ... At this point I installed Excel 2003 alongside my Office 2007 install. ... Yes, both versions of the Excel PIAs are present - however, Excel 2007 installs with the PIAs some redirect assemblies which mean that when an application requests an Excel 11 PIA, they're redirected to Excel 12. ... I noticed yesterday that actually the file this refers to in the Properties view of this reference is the 12 version. ...
    (microsoft.public.dotnet.framework.interop)
  • Re: OLE problem? Cannot insert table into excel cont...
    ... It sounds as though some of the Registry setting in Office are pointing to the wrong application. ... Especially if you install an earlier version after a later version. ... I go to insert/table/excel spreadsheet, it will then work but if I close out ... It is like word is trying to open excel 03 through dde or whatever ...
    (microsoft.public.word.application.errors)
  • Re: Problem opening Excel 2007 files
    ... Same problem exactly with full Office 2007 install on new install of Vista ... exposing an issue in Excel). ... status bar. ...
    (microsoft.public.excel.misc)
Loading