Aug 16th, 2009, 10:57 AM
Hey walkingby,
Drat, didn't realize I missed your post.
Neat problem... so I guess there's no way to modify that other script to accept a different database table name? Probably not, I suppose.
Unfortunately, Form Tools has a similar requirement: the form table names MUST be named like that: [prefix]form_[form ID]. All of the code relies on that, so changing it would require a fairly large overhaul of the script.
One option would be to create a duplicate of the Form Tools form table and grab the data from that. This may not work depending on your requirements, but you could rig up a simple cron job to automatically purge the new database and re-input all the current form tools data, say every day or hour or something. This isn't too tricky to get up and running, actually - the SQL is quite simple.
Other than that I don't have much to suggest... but good luck!
Ben
Drat, didn't realize I missed your post.
Neat problem... so I guess there's no way to modify that other script to accept a different database table name? Probably not, I suppose.
Unfortunately, Form Tools has a similar requirement: the form table names MUST be named like that: [prefix]form_[form ID]. All of the code relies on that, so changing it would require a fairly large overhaul of the script.
One option would be to create a duplicate of the Form Tools form table and grab the data from that. This may not work depending on your requirements, but you could rig up a simple cron job to automatically purge the new database and re-input all the current form tools data, say every day or hour or something. This isn't too tricky to get up and running, actually - the SQL is quite simple.
Other than that I don't have much to suggest... but good luck!
Ben