I developed an accounting app with a desktop db program called paradox.
The IDE integrates a native database + forms + reports.
My app consists of about 20 tables + 20 forms + 30 reports.
Paradox is an object oriented programming environment.
I've been studying the Rev demo and reading the user guide and other resources.
I'm concerned about using/learning Rev + SQLite + someReportSoftware
has anyone developped a similar project? Is Rev a good solution for me?
Thanks!
Jim
switching from Paradox to rev?
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller
-
Janschenkel
- VIP Livecode Opensource Backer
- Posts: 977
- Joined: Sat Apr 08, 2006 7:47 am
- Contact:
Hi Jim,
Revolution is an excellent choice for developing database front-ends. But you have to bear in mind that Revolution is a general-purpose development tool that also talks to databases - and as a result, won't be as tightly integrated with the db engine as Paradox was.
You'll have to write your own SQL queries, from SELECT to UPDATE statements. But don't take this as a discouragement, scripting is easy enough even if you may have to do a little more of it. My background is in developing database-backed applications and you'll have a working app far more quickly than if you try to rebuild it using .NET or Java.
If my memory serves me well, the University of Vienna rebuilt its entire student admiistration in Revolution+Oracle. The inEntertainment application is built using Revolution+MySQL. And there are plenty of other Rev-based apps that serve as custom database front-ends.
<shameless plug>
As for reporting tools, I happen to be the developer of Quartam Reports, which works similar to the reporting tools in Access and FoxPro - so give it a whirl, you'll feel at home.
</shameless plug>
Anyway, hop into the rev pool - the water's nice...
Jan Schenkel.
Revolution is an excellent choice for developing database front-ends. But you have to bear in mind that Revolution is a general-purpose development tool that also talks to databases - and as a result, won't be as tightly integrated with the db engine as Paradox was.
You'll have to write your own SQL queries, from SELECT to UPDATE statements. But don't take this as a discouragement, scripting is easy enough even if you may have to do a little more of it. My background is in developing database-backed applications and you'll have a working app far more quickly than if you try to rebuild it using .NET or Java.
If my memory serves me well, the University of Vienna rebuilt its entire student admiistration in Revolution+Oracle. The inEntertainment application is built using Revolution+MySQL. And there are plenty of other Rev-based apps that serve as custom database front-ends.
<shameless plug>
As for reporting tools, I happen to be the developer of Quartam Reports, which works similar to the reporting tools in Access and FoxPro - so give it a whirl, you'll feel at home.
</shameless plug>
Anyway, hop into the rev pool - the water's nice...
Jan Schenkel.
Quartam Reports & PDF Library for LiveCode
www.quartam.com
www.quartam.com
Ouch!
I've done some paradox-to-runrev conversion before, so I can assure you that it can be done. But it's not a lot of fun. It's a good idea to think about alternatives to paradox, as Corel seems to have dropped the ball on upgrades/bug fixes some years ago now. We have a large Paradox application which now hands off some data tasks to runrev modules.
Converting the data to another database is relatively straightforward. And converting the forms isn't all that hard. But your ObjectPAL code may be a different matter. For instance, if you're doing a lot with TCursors you'll have to rethink some things. You may want to think about starting fresh rather than translating what you've already written - it will probably be faster, easier, and you can benefit from what you've learned writing the Paradox app in the first place.
As Jan mentioned, the best thing may be to export your data to MySQL or something similar, then check out Quartam Reports to see if that will meet your reporting needs.
I've done some paradox-to-runrev conversion before, so I can assure you that it can be done. But it's not a lot of fun. It's a good idea to think about alternatives to paradox, as Corel seems to have dropped the ball on upgrades/bug fixes some years ago now. We have a large Paradox application which now hands off some data tasks to runrev modules.
Converting the data to another database is relatively straightforward. And converting the forms isn't all that hard. But your ObjectPAL code may be a different matter. For instance, if you're doing a lot with TCursors you'll have to rethink some things. You may want to think about starting fresh rather than translating what you've already written - it will probably be faster, easier, and you can benefit from what you've learned writing the Paradox app in the first place.
As Jan mentioned, the best thing may be to export your data to MySQL or something similar, then check out Quartam Reports to see if that will meet your reporting needs.