Ahmed thanks for your comments,
the situation is that before calling "searchMember.php" or
"searchProduct.php" or other, I need to give to user an interface where
a message like "insert the Product/Member/Order Id", then when he
inserts and presses "find" the appropriate "searchSomething.php" page is
called, depending on what whe had selected to search for.
Of course I can make 3 individual pages ("SearchProductIsertId.php",
"SearchMemberInsertId.php", "SearchOrderInsertId.php"), where each page
will call another page (e.g "SearchOrderInsertId.php" ->
"SearchOrder.php"). This seems easier but if a change is needed in
"SearchSomethingInsertId.php", I'll have to change all the 3 previous
pages. Thus I thougt it would be better to make only one page for all
searches.
What is the common choice of experienced php devs in case of creating an
administrative interface for various tables (e.g. products, members,
orders etc)?
Thanks,
Christos Korakidis
ahmed wrote:
> On 11/19/05, Webmaster <webmaster@xxxxxxxxxxx> wrote:
>>You can send data to the next php file by HTTP-GET.
>>Simply add a ? behind the link and then <variablename>=<value>.
>>Example ./jumpto.php?to=searchProduct
>
> Well i think it was about the code inside the search/add/edit pages
> not how to reach them.
> If i understood correctly, you're trying to reduce the amount of code
> to write by applying a pice of common code on your objects
> (product/member/order) while adding specific functionality using a
> switche specifed as a paramter (?object=Product/Member/Order)... It
> just all depends on "how common" are these operations that needed to
> be applied in each case.. so you knows that better
>
> -ahmed
>
>
> --
> <b>ahmed</b>
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
