Click here to Skip to main content
15,891,136 members

Comments by Leeland Clay (Top 12 by date)

Leeland Clay 7-Dec-11 19:42pm View    
If I'm understanding what you're doing, you can't use Session variables because you're working with a different server. When I worked with other payment services, I used hidden form fields that that it would be accessible within the view state.
Leeland Clay 7-Dec-11 13:33pm View    
I don't see a control named "txtContractorNumber" being declared within the TabPersonal container. If you actually intend to use the txtVenderNumber control, then you would use the following command:

<pre>
txtVendorNumber.Text = dr("ContractorNumber")
</pre>

You don't need to use FindControl when using ASP.Net Controls.
Leeland Clay 7-Dec-11 10:22am View    
You're Welcome Hernan. I'm glad you got it figured out. If possible, you should mark the question as resolved so that others can learn from it as well. If that's not an option, I'd suggest copy & paste your previous comment into the solution area so that it shows as answered.
Leeland Clay 7-Dec-11 7:47am View    
Hi Hernan,
Can you pull the IIS logs for the time that the error occurs and see if there's something happening in the background that is causing this? Normally, I see this error when someone forgets to test whether the session variable is null or not, but you're doing that. My thought is that maybe something is happening at the server level that is erroring out, and this cryptic message is just the result of that.
Leeland Clay 6-Dec-11 17:19pm View    
Personally, I'm not a fan of casting an object as you assign it to a property. In the Else block, try declaring a DataTable, then casting the session variable to the newly declared datatable, then assign it to the GridView1.DataSource.

Else
Dim dtable As DataTable
dtable = CType(Session("VolumeDataTable"), DataTable)
GridView1.DataSource = dtable