.accde packaging version issue

  • Thread starter Thread starter Matt
  • Start date Start date
M

Matt

I could not package an accde file with the runtime and deploy it effectively.
Problem - I was running Access 2007 SP1, and the Access2007Runtime. The
Access2007Runtime SP1 has just recently been released. That works. Just in
case anyone else was getting irritated...
 
Do you really need to use the package and deployment crap?
Honestly-- I don't think that it is necessary or helpful. Ever.
Period.

I personally prefer installing the runtime and then emailing the guy
the frontend (I mean ADP)

;)

-Aaron
 
I think you are working under the assumption that the person receiving the
files knows what the heck to do with them. Seriously, the package is
imperative to me not having to answer thirty stupid @$$ questions. I deploy
to all different levels of users, some are shop employees, so...I package my
stuff. I have had to help some of these guys log in. More than once.
--
"The only thing worse than an employee that just quits and leaves, is an
employee that quits and doesn''t leave."


[email protected] said:
Do you really need to use the package and deployment crap?
Honestly-- I don't think that it is necessary or helpful. Ever.
Period.

I personally prefer installing the runtime and then emailing the guy
the frontend (I mean ADP)

;)

-Aaron
Click to expand...
 
It just really blows my mind.

I mean-- the AccessRT.msi.. I mean.. it's a MSI file, right?

So-- In ActiveDirectory-- without _ANY_ other tools-- you can
distribute a MSI to all of your machines without writing a lick of
code.

_RIGHT_?

It's called a MSI.

If you call my bluff-- It will take me a couple of hours to find more
info on it-- but I swear to god it's true.

So now _WHY_ do you have to give people installers to merely have a
new copy of the front end?

I'd personally just put them in peoples home drives ;) ADP files work
like a charm.

-Aaron
 
Back
Top