Ilalove
asked on
Urgent: maybe someone already dealt with am issue like this one?
In one module of an application I am building (I already developed it using ASP at the server side) I offer to the the user (that is a seller) the possibility to set a certain number of custom views: custom views are customized ways a seller can view data (formatted in a classical HTML table) related to his clients.
On these data I am giving to the user 2 kind of possibilities of customization:
1) one related to WHICH columns (of the table containing the client data) he wants to view;
2) the other related to the ORDER under the which he wants those columns to appear in the table.
Even though - as I previously said- I already developed this module, I would like to optimize it some way by wrapping the whole in a COMponent.
A solution to which I an thinking about is the use of metadata (the name and the order of the colums) and/or maybe uthe use of an XML file that will store the preferences setted by the user: this file will have to be updated each time an user set a new custom view or modify an existent one.
Just a note: the values that will have to be passed to the COMponent are also: the seller ID (because the app will be used by many clients) and the viewID (because
each custom view will have its own view ID).
Thanks in advance.
Regards
KS
On these data I am giving to the user 2 kind of possibilities of customization:
1) one related to WHICH columns (of the table containing the client data) he wants to view;
2) the other related to the ORDER under the which he wants those columns to appear in the table.
Even though - as I previously said- I already developed this module, I would like to optimize it some way by wrapping the whole in a COMponent.
A solution to which I an thinking about is the use of metadata (the name and the order of the colums) and/or maybe uthe use of an XML file that will store the preferences setted by the user: this file will have to be updated each time an user set a new custom view or modify an existent one.
Just a note: the values that will have to be passed to the COMponent are also: the seller ID (because the app will be used by many clients) and the viewID (because
each custom view will have its own view ID).
Thanks in advance.
Regards
KS
what is your question? one quick thing to note when you are developing dll's for asp you can not specify data types in your parameters... they have to all be variant because vbscript does not allow type casting.
ASKER
I am interested in having at least a scheleton of code that manages the above scenario.
Thanx for your kind attention.
Regards
Davide
Thanx for your kind attention.
Regards
Davide
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.