Okay, well, I can only assume I'm following what's going on/what you're
trying to do.
Remember that pages are rebuilt each time by the ASP.Net runtime you make a
page request - that means that if you go to another page, even if it uses
the "same" master page, it's really a completely seperate instance of that
master page class - so you're really doing no good by setting property
values on that class because the second time everything will have been
recreated for you by scratch.
I haven't done much server farm development so someone else might offer a
better solution, but maybe store something in your query string?
Again, I'm not totally following every inch of what your'e trying to do. I'm
not as good when the code isn't right in front of me....
--
~~~~~~~~~~~
Ben Rush
http://www.ben-rush.net/blog
"Matt" <me*******@Hotmail.comwrote in message
news:11**********************@q75g2000hsh.googlegr oups.com...
On Apr 7, 2:44 am, "Matt" <meteha...@Hotmail.comwrote:
>They might move the application on farm later so i did not wanted deal
with session or cookies.
Though i will try view state.. Thanks for that.
I am confuse that i cant receive the master page property on second
page / link
Master.AppID is getting me the value though i have it available on
intellisense
Would there be a better design or solution for this..
Create 5 link/job page. Do the jobs on those pages for that ID..
Since this is second link second page, I dont have the ViewState
information on second page
view state is no good