Hi there. I am hoping someone can help me.
I have been hired to build a web front-end to an existing (very small) Progress application. The current application was built in Progress, with an 8.2a backend.
The technical environment for the web server is Windows 2000 / ASP. The database server is on a remote NT 4 machine. We also have a WebSpeed transaction server on a separate machine, which is able to talk directly to the Progress RDBMS.
Some of the possibilities are:
1. Do this entirely in WebSpeed.
2. Do the front-end in ASP, and connect over ODBC (through a DSN) to Progress 8.2a, using a Merant or OpenLink driver.
3. Do it in ASP, but connect by using WSASP.dll to connect to the WebSpeed transaction server, and have that execute the queries against Progress.
The major issue is: can WebSpeed execute the same files that the regular Progress client does? If so, I can re-use the existing files from the client-server app, which have already been written to handle inserts and queries in the correct way. If not, I have to re-write all the SQL and pursue option 2.
If anyone has any ideas, I would be extremely grateful to hear them.
Regards,
Rhys Weekley
I have been hired to build a web front-end to an existing (very small) Progress application. The current application was built in Progress, with an 8.2a backend.
The technical environment for the web server is Windows 2000 / ASP. The database server is on a remote NT 4 machine. We also have a WebSpeed transaction server on a separate machine, which is able to talk directly to the Progress RDBMS.
Some of the possibilities are:
1. Do this entirely in WebSpeed.
2. Do the front-end in ASP, and connect over ODBC (through a DSN) to Progress 8.2a, using a Merant or OpenLink driver.
3. Do it in ASP, but connect by using WSASP.dll to connect to the WebSpeed transaction server, and have that execute the queries against Progress.
The major issue is: can WebSpeed execute the same files that the regular Progress client does? If so, I can re-use the existing files from the client-server app, which have already been written to handle inserts and queries in the correct way. If not, I have to re-write all the SQL and pursue option 2.
If anyone has any ideas, I would be extremely grateful to hear them.
Regards,
Rhys Weekley