Progress and Visual Studio 2005

R

Ryan_sa

New Member
Hi Every1

I am a junior progress develper working in in Progress 9D.

My question is,

I am doing a project in C# using Visual Studio 2005. I am creating a Windows application. Applciation connects to database and does what eva it needs to do.

I would like to use Progress as my database instead of SQL Server as all our DB's are in Progress. They are all Progress 9d at the moment but will prob go to Openedge in the near future.

Does any1 know of any liks,articles etc that explain any of this?

Thanx Ryan.
 
Ryan_sa said:
Hi Every1

I am a junior progress develper working in in Progress 9D.

My question is,

I am doing a project in C# using Visual Studio 2005. I am creating a Windows application. Applciation connects to database and does what eva it needs to do.

I would like to use Progress as my database instead of SQL Server as all our DB's are in Progress. They are all Progress 9d at the moment but will prob go to Openedge in the near future.

Does any1 know of any liks,articles etc that explain any of this?

Thanx Ryan.
Click to expand...

I would also liketo know this.
 
Hi,

Depends on what you call "connect". But with the .NET open client you can talk with a Progress DB. There are many examples out there on making a .NET UI on a Progress db.
Search for ".NET open client" at psdn.progress.com.

If you want to write the BL aswell in C# then you can connect to the Progress database with the use of SQL.

In both cases there is need to upgrade to OE10.1B.

Regards,

Casper.
 
Hi,
As Casper mentioned, today there are two options:
a) .Net Open Client - This involves writing business logic in Progress ABL (formerly 4GL) and then making a dll available that accesses this business logic via the Progress AppServer. This is the method Progress would strongly suggest as it allows your Progress Developers to write the Business Logic Interface and only the UI is in .Net. This is especially valuable as the AppServer is the center of the progress world (in many ways). The same Business logic that the .Net interface is accessing, can also be made available to Java, WebServices and the Progress clients (Client Networking, WebClient or WebSpeed for Web Access). The other advantage of this is that you use the current 4GL triggers. Also in OpenEdge 10 there is a ProDataset that maps very nicely to the .Net Dataset

B) the other access method is via SQL92 which you do via the ODBC Data Provider. If you are doing updates via this interface, you would need any tiggers to exist as Java triggers as well as ABL Triggers.

On top of these, some time next year, progress is coming out with a .Net interface for Progress that runs via the Progress RunTime client and allows the UI to be written fully in Progress but produce a .Net UI.

HTH
Molly
 
You must log in or register to reply here.
Back
Top