M
Mark Davies
Guest
Hi Robert, It probably depends on what your intention is with this temp-table. If it used to be shared it probably means that you needed to somehow share the data between different procedures in a session? So, a few ways depending on how you intend to use your temp-table: 1. You can define it in your class and have a method to output the temp-table to whatever else needs it. You would probably do this as BY-REFERENCE / BIND - you will have to share the instance of the object with your temp-table in it 2. If this is session-wide you might want to make it STATIC and use it that way 3. Go all OO on it and create a class object that does all the work on the temp-table, such as CRUD and worker methods and then only interact with the class to work on the temp-table. This class would probably be static or you alternatively you just need to keep your instance available throughout the session or processes where you need it. When migrating to OO it is always best to plan ahead - this takes a bit more time, usually much more than what you are used to with procedural coding, but it allows you to break it up into smaller components that makes them far more reusable in the end. Hope that helps
Continue reading...
Continue reading...