[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
>
>----- Original Message -----
>From: "Mark Simms" < marksimms at verizon.net >
>To: "Access Developers discussion and problem solving" < accessd at databaseadvisors.com >
>Sent: Sunday, January 26, 2014 10:11:50 AM
>Subject: Re: [AccessD] Problem of a listbox's response on network... Part 1
>
>Thanks Jim - and this implies anyone migrating from MDB to Oracle or SQL
>Server has a complete rewrite on their hands as far as VBA-based data
>retrieval, correct ?
>
>>
>> Hi Mark:
>>
>> It does depend on where your program is pulling data.
>>
>> There is no substitute for speed when a local DAO connection is pulling
>> and displaying a single record or small group of records from a local
>> MDB database but have a DAO connection download 15K of records from a
>> remote server and fill a table with the results...
>>
>> An ADO connection can do that in one to two seconds. It is like
>> comparing a sports car to an 8 wheel semi, when it comes to moving
>> data.
>>
>> Jim
>
>