A Framework for Datadriven Forms for VB Dot Net

Hello All,

I am currently in the middle of creating a 'Framework' for my latest VB.Net
project.

I have always created such a tool for previous lauguages.

This time I am basing it on n-Tier architecture. I will probably continue
and develop my own version, but have any of you people developed your own
version, or used and 3rd party tools.

What I am referring to is a set of code that can be used for most forms in
the application, they will display data, allow for additions, deletions,
updates, will support record selection, etc.

I typically then add error logging, application logging, and a few other
minor features.

The only problem is it is a little labourious creating all the code for each
layer, and the stored procedures required, and the stored procedures for the
combo's also.

I am attempting to use .Net 2003's data adapter to generate some of the sql
for the updates and deletions, but I still have to hand write a reasonable
amount of the code myself.

Any thoughts?

Thanks in advance

Mark Breen
Ireland

Cor
Fri Jan 06 16:45:50 CST 2006

Mark,

Did you ever look at MS-Access, that is not written and maintained by one
man.

As well was the code for that not supported in a newsgroup.

I hope this gives an idea.

Cor

Senthilkumar
Wed Jan 11 22:43:58 CST 2006

Hi,

There are atleast 2 third party softwares that come to mind

1. Deklarit - www.deklarit.co,
2. ComponentOne - www.componentone.com - DataObjects.

I have tried both of them, and found componentOne dataobjects very useful.

Hope this helps.

Senthil


"Mark L. Breen" <mark.breen@nospam-gmail.com.off> wrote in message
news:eQglwEuEGHA.524@TK2MSFTNGP09.phx.gbl...
> Hello All,
>
> I am currently in the middle of creating a 'Framework' for my latest
> VB.Net project.
>
> I have always created such a tool for previous lauguages.
>
> This time I am basing it on n-Tier architecture. I will probably continue
> and develop my own version, but have any of you people developed your own
> version, or used and 3rd party tools.
>
> What I am referring to is a set of code that can be used for most forms in
> the application, they will display data, allow for additions, deletions,
> updates, will support record selection, etc.
>
> I typically then add error logging, application logging, and a few other
> minor features.
>
> The only problem is it is a little labourious creating all the code for
> each layer, and the stored procedures required, and the stored procedures
> for the combo's also.
>
> I am attempting to use .Net 2003's data adapter to generate some of the
> sql for the updates and deletions, but I still have to hand write a
> reasonable amount of the code myself.
>
> Any thoughts?
>
> Thanks in advance
>
> Mark Breen
> Ireland
>

Mark
Tue Jan 31 08:33:45 CST 2006

Hello Cor,

I have no idea what you mean with the two lines below, would you clarify if
you do not mind.?

Thanks in advance for your time

Mark


"Cor Ligthert [MVP]" <notmyfirstname@planet.nl> wrote in message
news:OQo3cLxEGHA.4036@TK2MSFTNGP09.phx.gbl...
> Mark,
>
> Did you ever look at MS-Access, that is not written and maintained by one
> man.
>
> As well was the code for that not supported in a newsgroup.
>
> I hope this gives an idea.
>
> Cor
>
>

Cor
Tue Jan 31 09:04:03 CST 2006

Mark,

In my idea do you take a to difficult problem to solve.

It looks for me as MS Access, however with building and maintaincing that
product is a large Microsoft team busy.

That code is absolute not for free, people who build that, try to get a
living from that.

That was what I did mean with this.

Cor

Mark
Tue Jan 31 10:24:30 CST 2006

Hello Cor,

Yes, I agree with you, but....

what do we do when we start an application with 25 - 30 forms, most of them
similiar.

I have created (or at least I am in the process of creating) a standard bit
of code that handles this basic form handling,

I acknowledge, that I do not want to rebuild access, of course not. Also, I
acknoweldge that the more sophisticated I make the framework, the more
inflexible it becomes, however, it cannot be that I hand code each and every
form, so I am seeking a happy medium,

What do you think?

Mark


"Cor Ligthert [MVP]" <notmyfirstname@planet.nl> wrote in message
news:uIR37dnJGHA.1424@TK2MSFTNGP12.phx.gbl...
> Mark,
>
> In my idea do you take a to difficult problem to solve.
>
> It looks for me as MS Access, however with building and maintaincing that
> product is a large Microsoft team busy.
>
> That code is absolute not for free, people who build that, try to get a
> living from that.
>
> That was what I did mean with this.
>
> Cor
>

Cor
Tue Jan 31 10:49:10 CST 2006

Mark,

For that is the inherited form

Try to do not to much on that however setting things as fontstyles, colors
etc is the least you can do.

You create a form and than you can use that by using the inherited form from
Add Items and it ask you what form should be used.

I tried to find an article for you on MSDN however could not find it fast.
Maybe can you search yourself for that. In fact it is reusing a form.

Cor



"Mark L. Breen" <mark.breen@nospam-gmail.com.off> schreef in bericht
news:OOkqVLoJGHA.3904@TK2MSFTNGP10.phx.gbl...
> Hello Cor,
>
> Yes, I agree with you, but....
>
> what do we do when we start an application with 25 - 30 forms, most of
> them similiar.
>
> I have created (or at least I am in the process of creating) a standard
> bit of code that handles this basic form handling,
>
> I acknowledge, that I do not want to rebuild access, of course not. Also,
> I acknoweldge that the more sophisticated I make the framework, the more
> inflexible it becomes, however, it cannot be that I hand code each and
> every form, so I am seeking a happy medium,
>
> What do you think?
>
> Mark
>
>
> "Cor Ligthert [MVP]" <notmyfirstname@planet.nl> wrote in message
> news:uIR37dnJGHA.1424@TK2MSFTNGP12.phx.gbl...
>> Mark,
>>
>> In my idea do you take a to difficult problem to solve.
>>
>> It looks for me as MS Access, however with building and maintaincing that
>> product is a large Microsoft team busy.
>>
>> That code is absolute not for free, people who build that, try to get a
>> living from that.
>>
>> That was what I did mean with this.
>>
>> Cor
>>
>
>

Mark
Tue Jan 31 11:46:42 CST 2006

Hello Cor,

Yes, that is something that I am considering, however, I still want to seek
the limitations of such an architecture, I am worried about building my
system with inderited forms and then finding that there is some property
that i wish to override and perhaps I cannot.

Mark


"Cor Ligthert [MVP]" <notmyfirstname@planet.nl> wrote in message
news:eXDPrYoJGHA.3984@TK2MSFTNGP14.phx.gbl...
> Mark,
>
> For that is the inherited form
>
> Try to do not to much on that however setting things as fontstyles, colors
> etc is the least you can do.
>
> You create a form and than you can use that by using the inherited form
> from Add Items and it ask you what form should be used.
>
> I tried to find an article for you on MSDN however could not find it fast.
> Maybe can you search yourself for that. In fact it is reusing a form.
>
> Cor
>
>
>
> "Mark L. Breen" <mark.breen@nospam-gmail.com.off> schreef in bericht
> news:OOkqVLoJGHA.3904@TK2MSFTNGP10.phx.gbl...
>> Hello Cor,
>>
>> Yes, I agree with you, but....
>>
>> what do we do when we start an application with 25 - 30 forms, most of
>> them similiar.
>>
>> I have created (or at least I am in the process of creating) a standard
>> bit of code that handles this basic form handling,
>>
>> I acknowledge, that I do not want to rebuild access, of course not.
>> Also, I acknoweldge that the more sophisticated I make the framework, the
>> more inflexible it becomes, however, it cannot be that I hand code each
>> and every form, so I am seeking a happy medium,
>>
>> What do you think?
>>
>> Mark
>>
>>
>> "Cor Ligthert [MVP]" <notmyfirstname@planet.nl> wrote in message
>> news:uIR37dnJGHA.1424@TK2MSFTNGP12.phx.gbl...
>>> Mark,
>>>
>>> In my idea do you take a to difficult problem to solve.
>>>
>>> It looks for me as MS Access, however with building and maintaincing
>>> that product is a large Microsoft team busy.
>>>
>>> That code is absolute not for free, people who build that, try to get a
>>> living from that.
>>>
>>> That was what I did mean with this.
>>>
>>> Cor
>>>
>>
>>
>
>