[AccessD] Re: [Private] Framework Discussion - Dependent Obje cts

MartyConnelly martyconnelly at shaw.ca
Wed Mar 17 16:11:30 CST 2004


You can get the Student Edition or Working Model of VB6 (no .exe 
creation or help files) included with
"Sam's Teach Yourself Visual Basic in 24 hours".  by Greg Perry ISBN # 
0672315335
Only $14 US.

DWUTKA at marlow.com wrote:

>Gustav, Gustav, Gustav....you need to invest in VB 6.  You could probably
>get it dirt cheap on eBay, and with your skills, you'll pick it up in a
>heart beat.
>
>A lot of people peg me as a VBer, simply because I use VB a lot.  However,
>I'm all for the right tool for the right job.  VB is just another tool.
>Now, if I could somehow merge the advantages of VB, with the advantages in
>Access, I would be a VERY happy camper!
>
>Drew
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Gustav Brock
>Sent: Wednesday, March 17, 2004 3:15 AM
>To: Access Developers discussion and problem solving
>Subject: Re: [AccessD] Re: [Private] Framework Discussion - Dependent
>Obje cts
>
>
>Hi Drew
>
>Yes, that makes sense to me, though I don't have any tools to program
>dlls. I have some very general and well proven functions which I
>simply keep collected in some modules which I copy-paste into a new
>project as needed - not very fancy, I know, but it works.
>
>/gustav
>
>  
>
>>I'm in the same situation as you. I find that building a 'framework' isn't
>>worth the effort, because I have to develop very diverse GUI's.  It's not
>>    
>>
>a
>  
>
>>matter of re-using features, it's a matter of building specific features
>>    
>>
>to
>  
>
>>handle the task at hand.
>>    
>>
>
>  
>
>>At my full time job, however, I have found that one of the best practices
>>    
>>
>I
>  
>
>>can stick too, is to develop applications as 'stand-alone' objects, yet
>>leave room for interaction.  So if I develop a library application for our
>>Drafting department, and later I develop a modeling package for the
>>engineers, if I need access to the drafting library, I can just
>>    
>>
>'reference'
>  
>
>>the drafting department's .dll's.  Makes life a lot easier.  To me, that's
>>what I call a framework.  It's not a generic thing from a functionality
>>standpoint, but more of a generic thing from a usability standpoint.
>>    
>>
>
>  
>
>>Make sense?
>>    
>>
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada






More information about the AccessD mailing list