Hi.
I'm designing an application with several parts to it. For this reason, we want to have an "Application Status" page where the applicant can see how far along the process they are. All I want this to say is very basically- the thing that needs to be done, and either YES or NO to see if its done.
The first thing that needs to be done is the php program I'm writing needs to automatically change the NO to a YES when that portion is done. Not a problem- I got that covered. Here's the fun part:
Some portions of the application are by mail-in. So we at HQ need to be able to get in and change the status through our own little form from NO to YES.
Essentially, my question is this: using hw_Modifyobject, what is objectID? The name of the table where the modifications are to be made? This is my thinking since the remove and add functions specify which fields to change. or do they not? I could be confused. (again). For reference sake, this is what phpbuilider lists as it's example for this function:
hw_modifyobject (int connection, int object_to_change, array remove, array add, int mode).
Now, second question, opinion question. As I'm building this, which is best/easiest. We have several people who will be using this application. Is it best to give them each their own table, or have one big table where each person's data is determined by their user name. Keep in mind all we have to do: They need to enter data AND view their status, and WE need to get in and view that status and change that status.
Any other hints, suggestions, comments, or clues are greatly appreciated.
Jeof Oyster
<!-- e --><a href="mailto:[email protected]">[email protected]</a><!-- e -->
I'm designing an application with several parts to it. For this reason, we want to have an "Application Status" page where the applicant can see how far along the process they are. All I want this to say is very basically- the thing that needs to be done, and either YES or NO to see if its done.
The first thing that needs to be done is the php program I'm writing needs to automatically change the NO to a YES when that portion is done. Not a problem- I got that covered. Here's the fun part:
Some portions of the application are by mail-in. So we at HQ need to be able to get in and change the status through our own little form from NO to YES.
Essentially, my question is this: using hw_Modifyobject, what is objectID? The name of the table where the modifications are to be made? This is my thinking since the remove and add functions specify which fields to change. or do they not? I could be confused. (again). For reference sake, this is what phpbuilider lists as it's example for this function:
hw_modifyobject (int connection, int object_to_change, array remove, array add, int mode).
Now, second question, opinion question. As I'm building this, which is best/easiest. We have several people who will be using this application. Is it best to give them each their own table, or have one big table where each person's data is determined by their user name. Keep in mind all we have to do: They need to enter data AND view their status, and WE need to get in and view that status and change that status.
Any other hints, suggestions, comments, or clues are greatly appreciated.
Jeof Oyster
<!-- e --><a href="mailto:[email protected]">[email protected]</a><!-- e -->