John R Ramsden
|
| Posted: 12/07/2002, 9:09 AM |
|
I have a page with links to another page that expects a query string
e.g. "msgreset.php?cust=dbsmith" where the 'cust' argument, 'dbsmith'
is the name of a database specific to a customer. (The databases for
all customers have the same structure; so the page works the same
with any.)
In the page msgreset.php I am fetching and parsing the query string
OK; but there doesn't seem to be a non-hack way to switch
connections from the database with which I set up the grid on
that page.
I started by adding an AfterInitialization event procedure; but that
didn't work. I then tried hacking the database initialization method
(which I was particularly keen to avoid having to do), to plug into
the initialization method the connection details for the new database;
but that also made no difference and the page obstinately continues
to stick with the original hard-coded database. (I specified this as
a persistent connection, which could have something to do with my
problems.)
For a product that prides itself on its database features it seems
amazing that one can't switch databases on the fly, as described
above. Can anyone offer any suggestions? TIA
Cheers
John Ramsden (john_ramsden@sagitta-ps.com)
|
|
|
 |
|
