[AccessD] Problem of a listbox's response on network... Part 1

William Benson vbacreations at gmail.com
Sun Jan 26 23:16:24 CST 2014


ditto, i see some at GE moving that way.
On Jan 26, 2014 7:53 PM, "Salakhetdinov Shamil" <mcp2004 at mail.ru> wrote:

>  Hi Jim --
>
> > I am leaning toward the Adobe suite...
> So do I.
>
> > ..almost as fast as an MS Access application...and only takes four/five
> times as long..
> I suppose that given nowadays developer tools (for all OSes and dev
> platforms/mainstream (general purpose) programming languages) it all
> depends on a developer skills. And no, I do not mean "junk FE Generations
> tools" - I mean (mainly) "hand-made" FE/UI/UX implementations.
>
> -- Shamil
>
> Sunday, January 26, 2014 3:57 PM -07:00 from Jim Lawrence <accessd at shaw.ca
> >:
> >Hi Shamil:
> >
> >No, in this case I was talking about the front or display end of the
> application. I do think the business intelligence and data management is
> all back end stuff. If done right a good balance between BI and DM can be
> made...I tend to "weight" processing towards the BE data server. I like to
> keep a clear separation between FE and BE, starting at the AJAX call...and
> try to keep these types of pages separated.
> >
> >As mentioned before, it is fun to build an ASP.Net application using VS
> (can be faster than hand coding), then go into the code dumping and
> separating the components depending on its location...client or server end.
> Though any automated building process tends to produce much more junk that
> useful code. It is not a pretty process but its fast (at least to
> build...not so fast to fix)...almost as fast as an MS Access
> application...and only takes four/five times as long...add to that bevelled
> and curved edges, field properties, shadows, background graphics, popup and
> help menus, images, smooth transitions and so on. ;-)
> >
> >Good or bad idea?
> >
> >What would you say is the best tool(s) set for building real, internet
> capable, applications with all the fancy and pretty interfaces, that
> customers now demand and expect and most importantly, will replace MS
> Access but for the browser?
> >
> >I am leaning toward the Adobe suite...
> >
> >Jim
> >
> >----- Original Message -----
> >From: "Salakhetdinov Shamil" < mcp2004 at mail.ru >
> >To: "Access Developers discussion and problem solving" <
> accessd at databaseadvisors.com >
> >Sent: Sunday, January 26, 2014 11:54:04 AM
> >Subject: Re: [AccessD] Problem of a listbox's response on network... Part
> 1
> >
> > Hi Jim --
> >
> >>>>  Coding in VB, C# or ASP.Net and so on,
> >>>> can take weeks to do what can be done days
> >Sorry? Do you mean that implementing ADO(.NET) manipulation of back-end
> databases in VB.NET, C# or ASP.NET (C#/VB.NET) "can take weeks to do what
> can be done (in) days" using MS Access pass-through queries, back-end SPs
> and VBA?
> >
> >Thank you.
> >
> >-- Shamil
> >
> >Sunday, January 26, 2014 12:38 PM -07:00 from Jim Lawrence <
> accessd at shaw.ca >:
> >>Hi Mark:
> >>
> >>Pass through queries can do a lot without re-coding. Deleting, adding
> and updating a single record can be handled just fine but when you start
> doing select statements, searches, multi-record processing and complex
> queries that is when the DAO application starts grinding to a stop.
> >>
> >>Once you have built a ADO based or mixed application, building another
> one is fairly easy as from then on it is mostly cut, paste and
> adjust...each new application becomes easier than the one before. :-)
> >>
> >>I think MS Access has one of the easiest interfaces of any database
> tool....ADO just allows it to connect to virtually any data source. Coding
> in VB, C# or ASP.Net and so on, can take weeks to do what can be done days
> and if you are going this route might as well build a JavaScript frame-work
> web interface.
> >>
> >>Aside: DDN is a great package but the over-head is huge. Put 100 users
> on a single application, you had better have your server fully deck-out and
> if anything fails...took me two weeks to solve one small issue as there are
> so many levels and so little internal documentation.
> >>
> >>Jim
> >
> >--
> >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
>


More information about the AccessD mailing list