No only will it not cause any problems, but it will server to separate your
presentation layer's presentation code (HTML) from the programming logic.
But, I would STRONGLY suggest you NOT access your data from the code-behind
of the .aspx page. You should create a separate data layer by writing the
data access stuff into a different class file.
"GP" <GP@discussions.microsoft.com> wrote in message
news:CF**********************************@microsof t.com...
Scott,
Thanks for your reply.I meant we are accessing the data using code behind
form.cs file ,form.aspx page acts as a presentation layer.Do you think
this
will cause any problems.
Thanks
GP
"Scott M." wrote:
No one ever accused Web Services of being the fastest or best performing
architecture, but they do solve some functionality issues. What using
web
services also does for you is give you the opportunity to break your code
up
into layers. It is generally recognized that having code that interacts
with
your data in the .aspx page (the presentation layer) is a bad thing.
"GP" <GP@discussions.microsoft.com> wrote in message
news:0A**********************************@microsof t.com... > We are connecting to sql server database in the webservices & retrieve
> the
> data
> as dataset from the webservices and load it to the aspx pages ,But we
> find
> loading of the aspx pages takes longer time than the pages that
> retrieve
> data
> directly using cs files.Is it good practise to use the data retrieval
> in
> web
> services.
> Can some help me in this issue.
> Thanks
> GP
>