Good, better, great!
You know, it only took me 2 years to find something on ADP's that you would
find "credible". There are others, however you will have to find those out
on your own...
If you are serious about doing some ADP testing, I would be glad to setup a
database and login for you - no problem, let me know and it's done. All I
ask is for an honest recommendation of my services to others if you find it
useful.
ASP.Net is a bombshell - but to be all around great, you really need either
a graphics person or to be adept in that profession. I think it's far more
technically in-depth than working with ADP's because you now have so many
more factors in place like IIS, enormous class libraries, third party
components to get showstopper features, and the most comprehensive IDE in
history. If you work with it everyday, you might start remembering what
things are and how to use them in about 6 months. Still, the downside of
the IDE is that while it promises to release a version that does... it will
not allow you to break-edit-continue, which is very mundane after being used
to debugging in vb/vba.
That said, if you just want to deliver some small apps and utilize your
Access background, then you can see that adp's are clearly meaningful.
I found some really great online conferences covering .net from the
Microsoft PDC 2003. A huge amount of sessions covering .net are available
for free - spoken in English by pro's with slides and screen action, and no
airline tickets involved :)
http://microsoft.sitestream.com/PDC2003/Default.htm
--
Jerry Boone
Analytical Technologies, Inc.
http://www.antech.biz
Secure Hosting and Development Solutions for ASP, ASP.NET, SQL Server, and
Access
"Larry Linson" <bouncer@localhost.not> wrote in message
news:WFqIb.20760$E17.10725@nwrddc02.gnilink.net...[color=blue]
> Jerry,
>
> Yours is the first, at least the first _credible_, account that I have[/color]
seen[color=blue]
> of actually using an ADP across the Internet. Having that rich-client work
> with a miserably slow connection (as any Internet connection tends to be,
> and dial-up IN SPADES) is indeed an advantage. So, I am going to have to[/color]
see[color=blue]
> what I can do about taking advantage of your pioneering experience -- I[/color]
may[color=blue]
> have to talk some colleagues into installing some things on a development
> server, so I can test over a real internet connection.
>
> It wasn't I who did the testing and offered the "revised" opinion on ADP[/color]
vs[color=blue]
> MDB, but some very knowledgeable and experienced folks within Microsoft (I
> am not at liberty to say who it is). Perhaps they were just talking about
> the "standard straight client-server on a LAN/WAN".
>
> In re: dot NET. As I have said all along, "for me, the saving grace may be
> that ASP.NET will make it simple(r) to create simple, modest web-based
> database applications". Now that the second version has been released, and
> we have seen some "peeks ahead" into the next version, it appears to me[/color]
that[color=blue]
> .NET is beginning to stabilize to the extent that they can do some work on
> the UI to make it easier and more usable for smaller users' applications,
> instead of _just_ worrying about making the whole "enterprise distributed
> app" thing work, which is my view of what's been going on up to now..
>
> Thus, I am beginning to take a closer look at ASP.NET, at the Visual[/color]
Studio[color=blue]
> environment, at Web Matrix, and at ADO.NET for accessing databases. In[/color]
fact,[color=blue]
> as the special interest groups in my user group have matured and evolved,[/color]
I[color=blue]
> am now an Assistant SIG Leader for the ASP.NET SIG. How's _that_ for a
> change in (apparent) position?
>
> Larry Linson
> Microsoft Access MVP
>
> "Jerry Boone" <jerry@antech.biz.killspam> wrote in message
> news:YuhIb.1228$GZ5.157@newssvr24.news.prodigy.com ...[color=green]
> > I have thought that for a[color=darkred]
> > > long time, and experienced Microsoft folk have just recently stated,[/color][/color]
> that[color=green][color=darkred]
> > > MDB-Jet-ODBC-server is better than ADP-ADODB-Server, in all[/color][/color]
> client-server[color=green][color=darkred]
> > > cases.[/color]
> >
> > (sorry so long Larry, I didn't abbreviate much here because I wanted to[/color]
> give[color=green]
> > you some real scenarios)
> >
> > I can think of one right off that your favored method isn't better - and[/color][/color]
I[color=blue][color=green]
> > don't expect you to care since you probably don't need to use it this[/color][/color]
way.[color=blue][color=green]
> > Using Access remotely over an internet connection. I have seen people
> > scratch their heads on this topic and nobody has any real solutions for[/color][/color]
it[color=blue][color=green]
> > other than having it hosted on a Terminal Server. No thanks, too many
> > security issues here for the hostee.
> >
> > So... it's better to me in these ways...
> >
> > ---------------------
> >
> > 1. Managed database services - Build a project and host the database.
> > Charge the customer for the delivered ade goods, then charge monthly for
> > hosting their data in a secure, web accessible style by giving them[/color][/color]
oledb[color=blue][color=green]
> > connection credentials from Sql Server. If they don't pay, back up the
> > database, burn it to disk, mail it, disable logins, done.
> >
> > 2. Web application data access - it's a showstopper... I give web app
> > customers one desktop icon to an ade with menu's and forms for updating
> > their web based data without telling them right away about what it does.[/color]
> I[color=green]
> > can tell you right now that the most satisfaction I have ever had[/color][/color]
(besides[color=blue][color=green]
> > you know what) is when showing the database to the customer, adding some
> > data, having them ask "how do we get that to the web?" and just saying -
> > "just hit refresh, it's already there"... "wow, your kidding me!! Wow,[/color]
> this[color=green]
> > is easy!!" - that isn't exaggerated one ounce... and is why I am[/color]
> successful[color=green]
> > at what I do. I can build the adp FAST and it works great. Also, I[/color][/color]
have[color=blue][color=green]
> > never heard a single complaint about corruption, crashes, or the[/color][/color]
inability[color=blue][color=green]
> > to connect.
> >
> > ----------------------
> >
> > You see, building bound mdb forms into the front end of a model that is
> > periodically "disconnected" over the "web" just doesn't appear viable[/color][/color]
with[color=blue][color=green]
> > mdb-jet-odbc (it just wasn't designed with this use in mind, dsn's are[/color]
> local[color=green]
> > to the machine they exist on) unless you scrap the Jet-Odbc part and[/color][/color]
build[color=blue][color=green]
> > it using ADO and unbound forms where Jet is removed as the transport and[/color]
> ADO[color=green]
> > recordsets are assigned to Access objects as recordsources. Andy B. and
> > Mary C. covered this pretty well in the book they did that covers
> > unbound/bound access mdb's and adp's. ADP's and SQL server are
> > significantly "better" here because of the very nature of the[/color][/color]
connection -[color=blue][color=green]
> > oledb.
> >
> > I can host SQL Server databases from my database servers and as long as[/color]
> port[color=green]
> > 1433 (or whatever port I choose to host sql on) is open, ADP's can[/color][/color]
access[color=blue][color=green]
> > the data and work over any Internet connection (yes, I even found dial[/color][/color]
up[color=blue]
> is[color=green]
> > not bad if you keep what you display to a reasonable amount) just as if[/color]
> they[color=green]
> > were sitting next to the server, using bound object methodology. In my
> > world, I can build an ADP, release it to my customer, and charge for the
> > application and monthly managed database services.
> >
> > We all sacrifice speed for the amount of code/features we[/color][/color]
execute/demand.[color=blue][color=green]
> > In that technical aspect, flat binary files would be even "better". But[/color][/color]
I[color=blue][color=green]
> > don't need to argue with you about it - I saw what you did to Kaplan[/color][/color]
when[color=blue]
> he[color=green]
> > was trying to get you to look at .net... I think he nearly had an
> > aneurism... unfortunately I believe I would suffer the same fate[/color]
> convincing[color=green]
> > you that adp's and sql server are better... or a php developer telling[/color][/color]
me[color=blue][color=green]
> > that .net is not better... so the differences remain, oh well [sigh].
> >
> > In all, I feel that programming and databases are just tools that can
> > consume thousands of hours in training to become truly proficient. I[/color][/color]
have[color=blue][color=green]
> > made 4 transitions in products over the last 7 years and it's really[/color]
> tiring[color=green]
> > as you more than likely know. I always thought plumbing would be good,[/color]
> the[color=green]
> > biggest change they made in 50 years was cast iron to plastic...
> >
> > The ADO code I threw in was merely a very stripped down way to hit Jet[/color][/color]
for[color=blue][color=green]
> > some data and loop it onto the page. There is absolutely nothing wrong[/color]
> with[color=green]
> > the code. I have used ADO literally inside-out to work with data, the[/color]
> suite[color=green]
> > of components are vital in my daily operations. I understand that you[/color][/color]
are[color=blue][color=green]
> > not up to this question, but thanks for checking it out.
> >
> > I appreciate your time and dedication sir.
> >
> > --
> > Jerry Boone
> > Analytical Technologies, Inc.
> >
http://www.antech.biz
> > Secure Hosting and Development Solutions for ASP, ASP.NET, SQL Server,[/color][/color]
and[color=blue][color=green]
> > Access
> >
> >[/color]
>
>[/color]
