Access SQL server from remote computer

[Jose Perdigao]

I hava an access ADP, now I woul like to access the back end in SQL server
2000 in my computer from a remote computer by internet to make testings. How
can I do? I would like to access by IP, is it possible?

Thanks
Jose

 

[Sylvain Lafontaine]

http://www.no-ip.com/

Don't forget to open the firewall for the port 1433 (if you have one). If
you are using an external modem with multiple ports or a router, you must
also configure them so that they will redirect any external connection to
your machine.

 

[Tom Ellison]

Dear Jose:

I have used VPN successfully for this purpose, and recommend that.

Tom Ellison

 

[Jose Perdigao]

it works fine,
thanks

Dear Jose:

I have used VPN successfully for this purpose, and recommend that.

Tom Ellison

 

[aaron.kempf]

yes; i was QUITE amazed with how well this works; i mean-- yet another
reason that ADP trumps MDB

 

[Tom Ellison]

My initial experiment with ADPs when they first came out was to try it over
VPN. Opening a rather complex form over VPN at a 500k byte connection with
a 10-15 second latency was a disaster with the MDB. The MDB must have
turned the line around several hundred times. It required about 75 minutes
to just open this form. The same form (very complex really) opened with the
ADP in 20 seconds. That's a better than 200:1 ratio of performance. This
is one of the reasons I immediately changed all development to ADPs, though
not the largest reason. There were many other reasons of performance and of
development efficiency that have made me very glad to have switched, some of
which are better than this 200:1 ratio.

BTW, this form takes about 4-5 seconds to open over a 100MB LAN. Obviously,
just reading the code and interpreting it is taking nearly 5 seconds.

Tom Ellison

 

[Tom Ellison]

Correction: 500K bit connection.

Tom Ellison

My initial experiment with ADPs when they first came out was to try it
over VPN. Opening a rather complex form over VPN at a 500k byte
connection with a 10-15 second latency was a disaster with the MDB. The
MDB must have turned the line around several hundred times. It required
about 75 minutes to just open this form. The same form (very complex
really) opened with the ADP in 20 seconds. That's a better than 200:1
ratio of performance. This is one of the reasons I immediately changed
all development to ADPs, though not the largest reason. There were many
other reasons of performance and of development efficiency that have made
me very glad to have switched, some of which are better than this 200:1
ratio.

BTW, this form takes about 4-5 seconds to open over a 100MB LAN.
Obviously, just reading the code and interpreting it is taking nearly 5
seconds.

Tom Ellison

 

[aaron.kempf]

Thanks Tom; i've been trying to say that for years now

so we got 3 votes for ADP and 0 for MDB.

 

[Tom Ellison]

Dear Aaron:

Well, my vote is strong for ADP given the applications I usually produce. I
still work in MDBs when required, and when appropriate. Both are very good
solutions for different purposes. The trick is to know when to use each.

Having used ADPs for some time, there is really no advantage in MDB if I am
the programmer. However, in simpler cases, where the advantages of an ADP
are not necessarily apparent, it is not justified to suggest that a
programmer needs to learn a largely new technology to little or no gain.
Many of the MVPs have seen this need and have learned ADPs or to use MDBs
with pass-thru queries to MSDE. They are not ingorant of it. But realize
that, in newsgroups other than those specifically for ADPs, nearly all the
questions are from programmers still strugling to learn MDBs. MDBs are
capable of performing what these programmers need, and is a good place to
start. Whether they ever need a more complex but more powerful platform is
uncertain. Most of them will never move on to anything like MDBs and SQL
Server. For those, like you, who have done so, I say "bravo" and I enjoy
your experience. But this will not do for those not ready to learn a new
level of technology, and who may never need it. You don't have to convince
me, but there's no need to try to convice them. They must be allowed to
develope skills naturally. Was it not at all like that for you? It was for
me!

Tom Ellison

 

[aaron.kempf]

i never would be a DBA today if i hadn't insisted on using ADP.

It just appals me that people run out and spend thousands of dollars on
toad and oracle.. when Access Data Projects have the best query design
tools anywhere

and i just swear; they just make way too many excuses for MDB

im tired of 'relink, refresh, reimport'
im tired of connection strings; i insist that ADP is inherently 10x
SIMPLER than MDB in the long run.

sure; parameters are a bear.

but when it comes to length of development vs. risk of losing data?

I believe that having a more robust db backend is always worth the
extra effort.

and query analyzer?

SOOOOOOOOOOOOOOOOOOOOOOOO much better; more powerful-- than MDB

 

[Tom Ellison]

Dear Aaron:

Much of what you say rings very true to me. Of course, QA is not in Access.
Not that I could live without it. And, as a tool, my opinion is that it
beats everything else I've seen. But then, I live in QA for days at a time.

It is not length of development that is the issue, I expect. It is the
"learning curve" for novices to become SQL Server DBAs, or the budget of
small companies to be able to afford one. So many Access applications are
written by John in the receiving departnemt, or Mary in accounting. There
can be considerable utility in that, and there can be disaster. Those of us
who try to support them in the NGs try to turn some of the failure into
success. Sometimes John or Mary go on to become adept, even expert, and a
few will become SQL DBAs and surpass us all. Others may be able to stop
pulling on their hair and get a good night's sleep. But, you cannot push
novices into ADPs and database administration (which so often means being a
senior database architect, rather than the guy who knows how to create and
run a backup script).

Your closing remark is mostly true, but not entirely. For what you do, and
for nearly all of what I do, it is better, and in all cases, more powerful.
But for a large number of people, it is not something they can handle, or
which they need or can justify. So, let them start up from something less
powerful, because it is simplified. It is not superior "in the long run"
but many of those are not in it for the long run. For them, the short run
is as far as they're going. Indeed, I expect this is the majority. They're
not going to become DBAs. They're not going to hire one.

That's my $0.02. I'll send you a bill if you send me your address.

Tom Ellison

 

[aaron.kempf]

i know that the learning curve for ADP is _LESS_ than the learning
curve for mdb

with mdb you spend all your time running around; learning workarounds.

can't stack select query on top of select query? change one into a temp
table..

bloating, refreshing, relinking, importing query defs?

ADP DOES IT ALL AUTOMAGICALLY

i am just stunned by the beauty of ADP sometimes.. i dont know how i
got by before this..
without ADP i would still be writing stupid little baby apps in mdb and
xls..

if we just set out these wimps to learn the RIGHT LANGUAGE the first
time; maybe everyone would be a lot happier in the long run

i've just seen too many dead-end access developers

and i know that ADP has _ALL_ the necessary features to make it easy on
newbies

i just.. i swear; i mean.. query analyzer rocks and it just boggles my
mind that kids still get into database by learning mdb.. it shoudl be
all about the adp boyzzzzzzzzzz

 

[Tom Ellison]

Dear Aaron:

Your points are valid, but not universally held. For persons of
considerable technical experience, your evaluation has considerable merit.
I agree with most of what you say as it pertains to developers with
considerable skills. I don't think most hold this true for the many novices
that come along. Few of them will ever progress to the level where ADPs are
something they'd be willing to tackle. Perhaps they would be better off if
they did try. But, clearly, that's not going to happen anytime soon.

Tom Ellison

 

[aaron.kempf]

i just argue that Microsoft should be marketing ADP towards newbies;
instead of their current policy-- not marketing Access in any way,
shape or form.

When was the last time we saw a Microsoft Access tv commercial?

an ad in an advertisement?

why isn't the Access Runtime more practical to distribute?

why isn't MIcrosoft held accountable for bugs in their software?

ADP is just a much better, more reliable; more functional stack than
MDB.

i mean.. views and sprocs beat MDB queries hands down.

Why is it that there ins't a single MVP that knows what an ADP is?

Why is it that Microsoft doesn't produce their financial apps USING
access data projects?

imagine, microsoft rewriting all their great plains apps to use Access
Data Projects.. that is the level of commitment that i'm looking for,
coming out of redmond

sell everyone the ADE version of it; and if they spend $100k then they
get the source.. i mean.. pretty cut and dry; isn't it?

USE YOUR OWN DOGFOOD?

it doesn't happen anymore.

Access Racism is more prevalent WITHIN redmond than anywhere else in
the world.
Why else do they BLOCK adp extensions via email?

Why can't we UPLOAD an ADP to a sharepoint site? Version control for
spreadsheet dorks?

I just claim that MIcrosoft is screwing the pooch; letting too many
people become Excel DORKS.. just because they're refusing to take
Access to the next level.

Excel is a disease.
MDB is a disease.

And Redmond is infected.. I say that it's bullshit that Redmond hasn't
released their SQL 2005 ADP patch yet.

SQLMAG.com says that 78% of people plan to migrate to SQL 2005 within
the next 12 months?

GIVE US THE TOOLS WE NEED _TODAY_ NOT IN THE NEXT VERSION OF OFFICE

this same bullshit is from the company that didn't have the foresight
to make SQL 2000 and Access 2000 compatable.

That right there, is an indicator that some fat and lazy Microsoft PM
needs to start pushing buttons in order to get this shit done.

I claim that I should be given a job as a Microsoft Product Manager;
kicking and screaming; with a team full of testers-- in order to make
sure that they raise the bar. STARTING IMMEDIATELY.

but no, what happens? I get FIRED for speaking the truth. I get FIRED
for complaining about SQL authentication.

Why is it that Microsoft gets such bad press for censoring a blog in
China; but then they FIRE SOMEONE FOR BITCHING ABOUT A CRITICAL
SECURITY FLAW THAT IS PUTTING OUR SOLDIERS AT RISK?

FIX SQL AUTHENTICATION MICROSOFT
START FIXING BUGS IN ACCESS

LAY OUT A ROADMAP-- WHAT ARE THE NEXT 20 YEARS OF MICROSOFT ACCESS
GOING TO OFFER?

I'm planning on writing Access Data Projects for the next 20 years.

Until Microsoft can produce something better than ADP; that will be my
meat and bones.

I dont care if i have to use SQL 4.2 to continue writing ADP.

Simple client-server; compete with an AS/400 Microsoft-- simple data
entry apps; simple bound data entry apps.


-aaron
ADP Nationalist