RAD apps for db development

[John]

Hi

Are there any RAD apps to speed up one-many db application development that
are worth considering?

Thanks

Regards

[Michel Posseth [MCP]]

VB.Net is a RAD ,,, i believe that this is the only true advantage of VB

"John" <Jo**@nospam.infovis.co.ukschreef in bericht
news:%2****************@TK2MSFTNGP03.phx.gbl...

Hi

Are there any RAD apps to speed up one-many db application development
that are worth considering?

Thanks

Regards

[Marc Greiner]

About your thread "Refilling dataset without changing context", you will also need to implement some locking mechanism, to protect the data integrity when several users edit the same record during the same period.
FYI XPO can handle such problems, which are always a pain in the neck when you need to program it yourself...

[Spam Catcher]

"John" <Jo**@nospam.infovis.co.ukwrote in news:#cxMKomaIHA.5348
@TK2MSFTNGP03.phx.gbl:

I think I am reasonably happy with the Infragistics controls
coupled with the standard code generated by vs 2008;

InFRIGistics.

I hate those controls. Overly bloated for nothing.

--
sp**********@rogers.com (Do not e-mail)

[Marc Greiner]

From what I understood from your other threads and this one, if you want to find the same easiness as in MSAccess, the only alternative you have today is the DevExpress XtraGrid in conjunction with XPO, used in server mode for big tables, and normal mode for small tables.

As I said, all what you need to do with the DevExpress Grid is bind your collection to the grid, set a few of its properties, and you are set. No SQL (no select, no insert, no update, no delete), and no code, no generated code, no dataset, you use real object collections.

With this, the user can edit directly in the grid with very nice editors (here I mean nicer ones).

The infragistic grid cannot do it, it does not know anything about Object Relational Maping and knows even less from Server mode.

I guess, if you are bound to a given control reseller, you won't be able to swap easilly for another one. I did it once (to be more precise, from infragistic to DevExpress) and it went very well for me.

[Michel Posseth [MCP]]

>PS: Not taken personally.

>
Good to hear, many times comments come across as personal attacks, and
I didn't want mine to be taken incorrectly.

People seem especially feeling this way , if you do not share there opinion
or views
Michel

"rowe_newsgroups" <ro********@yahoo.comschreef in bericht
news:d6**********************************@d21g2000 prf.googlegroups.com...

>Seth, I wrote one complete db app in vs2003 (access backend) and sold it
too
so its a commercial app but the time it took to develop and then to
support
it afterwards (to change only one field in a table I needed to change
tons
of data layer code) that it brought tears to my eyes.

Interesting, I've never noticed any really time consuming data access
tier changes, but I might be immune as I spend most of my day adding
such and such a field to such and such a table. But non-the-less, I
feel your pain when it comes to maintaining the code against db
changes.

>Sometimes I wonder why MS doesn't do an MS Access version with sql server
backend (instead of Jet)

I'm pretty sure, though not positive, that you can hook Access into
Sql Server. As a matter of fact, I think it has an upgrade wizard
built in.

>as Access does the routine db access stuff quite
nicely without having to write tons of code.

Well, I'll differ in opinion here. I hate to the bottom of my sole
(yes I mean the bottom of my shoe) the way Access handles db
interaction. It's a bad architecture in my opinion, but to each his
own.

>If it were possible to allow
developer write perfectly working db apps in 1997 (Access 97) then it
should
be possible in 2008 too. Not an unreasonable expectation.

Not unreasonable at all.

>PS: Not taken personally.

Good to hear, many times comments come across as personal attacks, and
I didn't want mine to be taken incorrectly.

Thanks,

Seth Rowe [MVP]

[Cor Ligthert[MVP]]

John,

If you want the "simple" solutions you can make with Access, this is can
"almost" be as easy as in Access with VB.

However, when people start with VB or a more to the code based program
language like that, then most people wants suddenly all other things they
never would think about in Access. Just because that is impossible.

You will say not true, this the standard behaviour of mankind.

Cor