App deployment

[John]

Hi

I have an access frontend/backend app which I update frequently to add new
features. At the moment, on a network with large number of client PCs I need
to copy the mde file individually on all pcs and create icon etc. Is there a
easier way to deploy an access app to multiple pcs in a network?

Thanks

Regards

 

[Albert D.Kallal]

There is a great "auto update" that updates the front end for you here:

 

[Albert D.Kallal]

There is a great "auto update" that updates the front end for you here:

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

 

[aaron.kempf]

use ADP it is a lot easier to deal with.

i mean-- you dont have to distro anything when you change a query.
because all the tables and queries are stored in one place.

and the database is about 3 times faster if you just bite the bullet
and learn ADP.

i mean.. MDB is a disease
aren't you tired of

a) queries crapping out
b) refreshing linking, updating
c) DSNs
d) versioning queries

you can still use their code if you want

but i mean-- the root of the problem is that MDB is a crap architecture.

 

[Tony Toews]

use ADP it is a lot easier to deal with.

ADPs have their good points and their bad poitns.

i mean-- you dont have to distro anything when you change a query.
because all the tables and queries are stored in one place.

You've never responded my previous postings on this topic.

It is very seldom that I just change queries. I'd also be updating forms, reports
and VBA code as well. So you'd still need to distribute new FEs be they MDBs or
ADPS.

and the database is about 3 times faster if you just bite the bullet
and learn ADP.

Database or development speed?

i mean.. MDB is a disease
aren't you tired of

a) queries crapping out

Really? The few times I've had troubles with queries I've figured out work arounds.
And these were very complex nested queries so nothing would've surprised me.

b) refreshing linking, updating

Updating is rather a broad topic. But as far as refreshing and linking goes what
happens when you change the SQL Server database from a test to live environment? You
still ahve the same issues.

c) DSNs

Who uses DSNs? Go DSN less

Using DSN-Less Connections
http://www.accessmvp.com/djsteele/DSNLessLinks.html
ODBC DSN-Less Connection Tutorial Part I
http://www.amazecreations.com/datafast/GetFile.aspx?file=ODBCTutor01.htm&Article=true
HOWTO: Use "DSN-Less" ODBC Connections with RDO and DAO
http://support.microsoft.com/?id=147875
ODBC DSN Less
http://www.able-consulting.com/MDAC/ADO/Connection/ODBC_DSNLess.htm

d) versioning queries

Repeat. It is very seldom that I just change queries. I'd also be updating forms,
reports and VBA code as well. So you'd still need to distribute new FEs be they MDBs
or ADPS.

but i mean-- the root of the problem is that MDB is a crap architecture.

Rubbish.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[aaron.kempf]

uh i can't go DSN less.. you see.. it's slower than a DSN right??

MDB IS A CRAP ARCHITECTURE.
IT DOESNT SCALE. IT DOESN"T WORK WITH A DOZEN USERS.


the point about Access queries-- you shoulnd't NEED workarounds.

Access ADP queries dont require workarounds. it is a much better query
engine; i mean.. WOW

and just for the record; it's easy to have ONE connection in an ADP
that points to test or prod or dev.

technically, test is a copy of production.

and dev gets versioned with every major release

i sure dont have versioning problems with SQL.. and i can keep track of
changes to data with TRIGGERS (if i need to)

MDB is just a waste of time; you must smoke crack kid

 

[aaron.kempf]

and WHICH previous post; i probably flame 50 threads a day

 

[Tony Toews]

uh i can't go DSN less.. you see.. it's slower than a DSN right??

Why is it slower? News to me.

MDB IS A CR(P ARCHITECTURE.
IT DOESNT SCALE. IT DOESN"T WORK WITH A DOZEN USERS.

Rubbish. I have clients with 25 users on it with no problems.

the point about Access queries-- you shoulnd't NEED workarounds.

Access ADP queries dont require workarounds. it is a much better query
engine; i mean.. WOW

I agree that queries have troubles is not good. But I've had so few of them it
hasn't been a problem for me.

and just for the record; it's easy to have ONE connection in an ADP
that points to test or prod or dev.

Ok, so that's a bit easier than relinking tables. Big deal.

and dev gets versioned with every major release

i sure dont have versioning problems with SQL..

What versioning problems are you talking about here?

and i can keep track of
changes to data with TRIGGERS (if i need to)

Sure, that's a minor point in favour of using SQL Server. Not a big deal to most
people.

MDB is just a waste of time; you must smoke crack kid

Wrong. MDBs suit the vast majority of users just fine.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[aaron.kempf]

im talking about linking, refreshing, DSNs.

im talking about changing Sql Passthroughs in order to fire a sproc.

it's just too complex, MDB against SQL Server. and it's not as
powerful.

 

[Tony Toews]

im talking about linking, refreshing, DSNs.

im talking about changing Sql Passthroughs in order to fire a sproc.

it's just too complex, MDB against SQL Server. and it's not as
powerful.

Please also respond to the other points I mention. Feel free to be quite specific.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Alex Dybenko]

Hi,

IMHO - this is only a first impression, at the end you will find that MDB
with SQL server is more efficient to deal with.

BTW, Tony - I only see your replies, and no OP posts - any idea why this?

 

[Douglas J Steele]

Tony's trying to get answers from Aaron Kempf, who appears to have succeeded
in getting himself banned from the msnews.microsoft.com server. I suspect
Tony gets his newsgroup feed from a different server.

 

[Tony Toews]

I suspect
Tony gets his newsgroup feed from a different server.

Correct.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[aaron.kempf]

in the end you'll find MDB against SQL _MORE EFFICIENT_

WHAT THE HELL ARE YOU TALKING ABOUT?

Le'ts just compare queries for a second
a) ADP wins the performance crown
b) ADP wins the simplicity crown - no SQL passthroughs
c) ADP wins the power crown - it's just blatantly more powerful because
you can use sprocs and views

 

[aaron.kempf]

yeah.. because MS is a bunch of drunks that are too proud to do
anything right

that company deserves a good old fashin whuppin and you guys; sitting
around and making excuses-- you're not helping the cause of Microsoft.

Microsoft isn't taking QUALITY serious enough
i mean-- a couple of years ago; they had that whole 'security centric'
rebirth

now they need to do the same thing for performance / quality /
usability

they have bugs bug bugs coming out of their ears; and now they're stuck
trying to automate everything with code.. they need to hire about
10,000 more testers is what they need to do.