Re: MultiValue Visual Basic
- From: "Dave Mitchell" <mitch500@xxxxxxxxxxxx>
- Date: Fri, 28 Oct 2005 00:52:30 -0400
Hi Tony,
Sory I don't time right at the moment to address everything you've
mentioned, so I'll just snip a couple of items and comment.....
>>In trying to wrap my mind around what you're saying, my guess is
>>that I should have a series of screen forms as the user interface, and
>>after
>>the user enters data, it is manipulated into some sort of pre-defined
>>object, and that object is then sent to another (Data Provider) procedure
>>which reads/writes/updates any type of database. Am I close??
>
> Yes, the user interface should not in any way know what kind of
> database you're accessing or how you're accessing it. A properly
> written n-tier model allows developers to completely swap out any
> component (UI, rules, data access, communications layers) without
> affecting the other components.
Thank you for clarifying that. I think I'm already writing code like that,
having come from UniVerse and preferring to write "Black-Box" type
subroutines. If I'm not actually writing code like that in VB yet, that's
at least that's my intention (before learning of some other way of doing
things and rewriting something....)
> Yup, COBOL, Fortran, RPG and about 15 other language/dialects here
> too. I think the order of the day is to learn what's required and
> focus on it intensely as much as possible. Being a generalist is cool
> but there's something to be said for having a specific set of skills
> that you're very good at.
I'm working towards becoming more of a generalist (starting with VB), but
right now my specific set of skills is STRONGLY biased towards
Pick/UniVerse, a platform which seems to be going away very quickly, at
least in my region of the world.
> You won't find much about PDP.NET with Google searches. If your
> company already has PDP.NET then check the online documentation, and
> dont hesitate to post a note to the RD forum or e-mail Support with
> questions - your company is already paying for it. If you don't have
> PDP.NET (or mv.NET or UO.NET etc) I'll be happy to exchange notes with
> you about your needs and where to find specfic info.
And therein lies the problem.... I have no employer. The company I was
with ditched their UniVerse payroll system back in March, and I was left
without a job (in fact, the entire office in my city has since shut down,
stranding more than just UV people). For the time being, I'm still
supporting some of the clients that were left hanging without support when
the company did that, but they are all migrating away from that system, so
this is only short-term. So basically, I would have no access to any of
that documentation. Although I have been using MSDN extensively to teach
myself VB6.
Thanks for all your help Tony - I think I'll toddle off to the bookstore
tomorrow and look for VB.NET for Dummies...
Dave
.
- Follow-Ups:
- Re: MultiValue Visual Basic
- From: Peter Schellenbach
- Re: MultiValue Visual Basic
- References:
- MultiValue Visual Basic
- From: Dave Mitchell
- MultiValue Visual Basic
- Prev by Date: Re: MultiValue Visual Basic
- Next by Date: Re: MultiValue Visual Basic
- Previous by thread: Re: MultiValue Visual Basic
- Next by thread: Re: MultiValue Visual Basic
- Index(es):
Relevant Pages
|