[AccessD] FW: Access 2007 (and other rants)

...I tried both Iron Speed and CCS as code generators and wound up throwing 
them out in favor of coding it myself ...just too many compromises and 
restrictions for me ...I wasn't willing to settle for what they put out and 
thus spent as much or more time customizing their code than if I'd just done 
it myself ...the real productivity tool for me was finding some really good 
net resources and then building my own code library ...once that was in 
place, I could really start using the huge variety of tools in the .net 
framework where a simple one liner can bring a lot more results than you 
could ever dream of in Access.

...I will make one comment though ...I knew AccessD was invaluable to me in 
learning and working with Access ...but it wasn't until I got into asp.net 
and c# and found no similar resource community that I realized just how 
valuable it truly was and remains even now ...don't know why that is but 
I've looked all over the net for more than a year now and just not found the 
equivalent ...not even close.

William

--------------------------------------------------
From: "Shamil Salakhetdinov" <shamil at smsconsulting.spb.ru>
Sent: Friday, April 25, 2008 3:30 AM
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] FW: Access 2007 (and other rants)

> Hi Doug,
>
> It's nearly as RAD as using MS Access - sometimes (much) quicker sometimes
> slower, but if one starts from zero level coming from VBA world then 
> rather
> long learning curve should be taken into account...
>
> Using native ASP.NET controls in web apps development didn't create any
> problems here with users working in IE7 (and IE6), FF, even Safari...
>
> To make simple ASP.NET application with just several (or even many) data
> entry/edit/retrieval forms is relatively easy task but making the same
> application ready to go scaled to enterprise level is a very different 
> task,
> which will take much more efforts, still with good experience in ASP.NET
> even enterprise level development could be as RAD as usual MS Access
> development...
>
> Consider using one or another third-party (or hand-made) code generators 
> and
> ORM frameworks: the LINQ for SQL, which MS targets to this ORM role 
> haven't
> yet got proven to be the best ORM framework/tool (but I must say I could
> have missed latest news/articles/books on this 'LINQ for SQL as ORM
> framework' subject)...
>
> --
> Shamil
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Steele
> Sent: Friday, April 25, 2008 6:02 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] FW: Access 2007 (and other rants)
>
> Does anyone have a rough idea of how long it takes to code a Web app 
> versus
> a comparable Access database?
>
> Doug Steele
>
> On Thu, Apr 24, 2008 at 4:54 AM, Susan Harkins <ssharkins at gmail.com> 
> wrote:
>
>> > ...otoh, I can't say enough good things about Visual Studio 8 and .net
>> > ...MS
>> > hit a home run there imnsho ...I'm moving clients into browser based
> apps
>> > as
>> > fast as I can write the code.
>>
>> =========The link I posted yesterday is about that very subject, only
>> specific to Access database applications.
>>
>> Susan H.
>>
>> --
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com
>>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>