Temp-Tables and Webspeed
- Thread starter andyb
- Start date
The 'screens' of a WebSpeed application are HTML pages. HTML pages don't have progress code in them. So there are no temptables to pass through.
What is the functional reason for the fact that you want to pass temptables between screens?
You probably want to keep track of some state or hold some nessecary information. To accomplish this you should use some kind of session management. With the out of the box session mangement provided by Progress you can store and retrieve data with the getsession en setsession functions. If you would have some more sophisticated session mangement you would probably use database tables to store and retrieve information.
Maybe if you clarify your problem I could be of more assistence...
Regards,
Casper.
What is the functional reason for the fact that you want to pass temptables between screens?
You probably want to keep track of some state or hold some nessecary information. To accomplish this you should use some kind of session management. With the out of the box session mangement provided by Progress you can store and retrieve data with the getsession en setsession functions. If you would have some more sophisticated session mangement you would probably use database tables to store and retrieve information.
Maybe if you clarify your problem I could be of more assistence...
Regards,
Casper.
Hello andyb,
I wrote our own version of webstate which is also tied to basic security features sometime ago.
That lets you either save state at the session or program level.
We group html pages in a single .p thats more of a stand alone program so that state and some security aspects can be managed per program.
We made our own customized copy of web-disp.p because all and every request go though this single entry point and its a very strategic place, so to speak.
That makes a call to load state from the database before calling the web object and saves state to the database after it has finished
In between all state read/write operations are done from memory.
It lets you save string fields and even large fields (separately) but theres nothing about saving temp-tables at least not directly.
But thats because some things that you may have done for example in GUI may not be suitable in a web app.
Contact me privately if you're interested in the programs.
I wrote our own version of webstate which is also tied to basic security features sometime ago.
That lets you either save state at the session or program level.
We group html pages in a single .p thats more of a stand alone program so that state and some security aspects can be managed per program.
We made our own customized copy of web-disp.p because all and every request go though this single entry point and its a very strategic place, so to speak.
That makes a call to load state from the database before calling the web object and saves state to the database after it has finished
In between all state read/write operations are done from memory.
It lets you save string fields and even large fields (separately) but theres nothing about saving temp-tables at least not directly.
But thats because some things that you may have done for example in GUI may not be suitable in a web app.
Contact me privately if you're interested in the programs.