vb .net web page error before page_Init with IE6

  • Thread starter Thread starter BoogieWithStu22
  • Start date Start date
B

BoogieWithStu22

I am running into a problem with a web page I have created when
viewing it in IE6 on some machines. The page has a database lookup.
The user enters an account name or number and clicks a lookup button.
This hits an AS400 database looks for matches and returns a dataset
that is used to populate a datagrid. The user then selects one of the
entries from the list, this entry is used to populate a couple of
textboxes on the page and a couple of textboxes in a usercontrol on
the page. The page has another database lookup. The user enters an
productname or number and clicks a lookup button. This hits an AS400
database looks for matches and returns a dataset that is used to
populate a datagrid. The user then selects one of the entries from
the list, this entry is used to populate a couple of textboxes on the
page and a couple of textboxes in a usercontrol on the page. The
problem is that on IE6 on some computers, the page runs the code to
lookup the data in the database, creates a dataset, binds the data to
a datagrid, and then IE6 freezes until it has to be closed due to not
responding. I have put in many many lines to log where I am at and I
IE is freezing after the page.dispose method is finished, but before
the next page_init is called.

The computers in question are using IE6 on XP Pro SP2. I use IE6 on
XP PRO SP2 here at work and everything is fine. I have also tried on
other computers using IE6, IE7, Firefox 1.x and 2.0 with no problems.
It is only IE6 on some machines. The processes for the account lookup
and the product lookup are identical except for the different tables
and fields.

So, what I am wondering is if there is anything that happens between
the dispose and page_init that I could try to intercept or if anyone
has heard of anything like this.

If you need code, let me know.

Please help. Thanks for reading this.

-Justin
 
I am running into a problem with a web page I have created when
viewing it in IE6 on some machines. The page has a database lookup.
The user enters an account name or number and clicks a lookup button.
This hits an AS400 database looks for matches and returns a dataset
that is used to populate a datagrid. The user then selects one of the
entries from the list, this entry is used to populate a couple of
textboxes on the page and a couple of textboxes in a usercontrol on
the page. The page has another database lookup. The user enters an
productname or number and clicks a lookup button. This hits an AS400
database looks for matches and returns a dataset that is used to
populate a datagrid. The user then selects one of the entries from
the list, this entry is used to populate a couple of textboxes on the
page and a couple of textboxes in a usercontrol on the page. The
problem is that on IE6 on some computers, the page runs the code to
lookup the data in the database, creates a dataset, binds the data to
a datagrid, and then IE6 freezes until it has to be closed due to not
responding. I have put in many many lines to log where I am at and I
IE is freezing after the page.dispose method is finished, but before
the next page_init is called.

The computers in question are using IE6 on XP Pro SP2. I use IE6 on
XP PRO SP2 here at work and everything is fine. I have also tried on
other computers using IE6, IE7, Firefox 1.x and 2.0 with no problems.
It is only IE6 on some machines. The processes for the account lookup
and the product lookup are identical except for the different tables
and fields.

So, what I am wondering is if there is anything that happens between
the dispose and page_init that I could try to intercept or if anyone
has heard of anything like this.
Click to expand...
No, I have never heard of this. That's why I never use datasets to do
anything. I always do everything by using an object or collection of
strong typed objects using the IList interface so that the collection
can be bound to a control, which the object or objects being derived
from a database source such as a table and the object can persist itself.

It also seems that you have all your code in the code behind file, data
access, etc, all of it the whole nine yards in the code behind file,
which is a no no too. Are you doing that? Are you treating ASP.NET like
it's ASP 3.0 or lower, with data access and validation of data being
done in the code behind file and the user interface is directly
instantiating data access?
 
IE6 and IE7 work best with VB6

dotnet is a futile experiment in mediocrity


sorry kids

move on to php or something; or else grow some balls and demand a
complete solution from M$
 
Back
Top