feedback request on design issue

[Guest]

Hey all,

Database Info:
I have an employee database management system.
There's about 8 tables that makes up a single record for an employee.

ASPNET:
I have a datagrid list of Employees.
When a user clicks on a particular employee an employee object will be
created.

Here's where I'm requesting feedback from you all:
I'd like to take the user to a tabbed page for the selected employee. I'd
prefer no postbacks as a user clicks the tabs (note: the tabs pretty much
represent a particular table in the database for that employee).

Now, I've heard the buzz word going around about Atlas. If I choose to go
with Atlas, does this mean I have to load up all the tables that comprise the
employee on the initial postback? And if so, for the collections involved,
would it be fine to have the actual objects loaded up in the collection (as
opposed to using a structure for quicker display purposes)?

thanks,
rodchar

 

[Guest]

Hey all,

Database Info:
I have an employee database management system.
There's about 8 tables that makes up a single record for an employee.

ASPNET:
I have a datagrid list of Employees.
When a user clicks on a particular employee an employee object will be
created.

Here's where I'm requesting feedback from you all:
I'd like to take the user to a tabbed page for the selected employee. I'd
prefer no postbacks as a user clicks the tabs (note: the tabs pretty much
represent a particular table in the database for that employee).

Now, I've heard the buzz word going around about Atlas. If I choose to go
with Atlas, does this mean I have to load up all the tables that comprise the
employee on the initial postback? And if so, for the collections involved,
would it be fine to have the actual objects loaded up in the collection (as
opposed to using a structure for quicker display purposes)?

thanks,
rodchar

 

[Guest]

please help on this one.