F
Frank Buchan
This is an odd one.
I have an application (rather large) that has a page where data from a
single dataset binds to two controls. The one control is a Calendar control,
which binds to the dataset directly. The other control is a DataGrid, which
is bound to the same dataset, though it is filtered via a DataView. On five
development boxes everything works perfectly. The Calendar and List fill,
without even a single issue. Using the same database (SQL Server 2000) on a
live server, the T-SQL that populates the dataset works perfectly, and
without errors. The Calendar control fills without error. The DataGrid
throws no exceptions, but just remains blank. Code inserted to determine if
the dataset is somehow over-filtered shows that it is not. Looping the rows
of the DataView produces a list identical to what is expected. Again, no
errors. None. And, yet, the DataGrid is frustratingly blank...until one sets
the filter controls (also part of the page) and clicks the Filter button. At
that juncture, the List fills, and the DataGrid behaves as it does on every
other box this has been checked against.
The code works, and there are no errors thrown on any of the machines; all
SQL Server installs are identical; all databases are identical; all code is
identical. Does anyone have any idea what could cause this bizarre
behaviour -- which cannot be reproduced on any other machine, no matter how
hard we have tried.
Thanks for any insight.
Frank Buchan
I have an application (rather large) that has a page where data from a
single dataset binds to two controls. The one control is a Calendar control,
which binds to the dataset directly. The other control is a DataGrid, which
is bound to the same dataset, though it is filtered via a DataView. On five
development boxes everything works perfectly. The Calendar and List fill,
without even a single issue. Using the same database (SQL Server 2000) on a
live server, the T-SQL that populates the dataset works perfectly, and
without errors. The Calendar control fills without error. The DataGrid
throws no exceptions, but just remains blank. Code inserted to determine if
the dataset is somehow over-filtered shows that it is not. Looping the rows
of the DataView produces a list identical to what is expected. Again, no
errors. None. And, yet, the DataGrid is frustratingly blank...until one sets
the filter controls (also part of the page) and clicks the Filter button. At
that juncture, the List fills, and the DataGrid behaves as it does on every
other box this has been checked against.
The code works, and there are no errors thrown on any of the machines; all
SQL Server installs are identical; all databases are identical; all code is
identical. Does anyone have any idea what could cause this bizarre
behaviour -- which cannot be reproduced on any other machine, no matter how
hard we have tried.
Thanks for any insight.
Frank Buchan