314 replies to this topic

[sportster]

I am using IE 7 for what that's worth

[jds]

I am using IE 7 for what that's worth

The browser shouldn't matter, seeing as how it's all server side code. Heck, I'm running it on FF and Safari on a Mac

[breeze]

BobWang doesn't like him?

[jds]

BobWang doesn't like him?

Wow - that took me a second, and it was based off my own joke. I must be tired.

[BobWang]

BobWang doesn't like him?

No, I have a special error message reserved for Rorer.

[sportster]

I used it with success with FireFox. I noticed in IE, there is a problem loading the initial page - warning down in the bottom left. Line 55, Character 1, "Object Expected".

[jds]

Bob - can you run that EQ listing on the previous page through on your end? It works for me, but apparently giving him problems.

[breeze]

[GonnaGetEm]

jds, it's working fine on my end.

[jds]

I used it with success with FireFox. I noticed in IE, there is a problem loading the initial page - warning down in the bottom left. Line 55, Character 1, "Object Expected".

Okay, I'll take a look in a little while.

Thanks for letting me know

[jds]

jds, it's working fine on my end.

What browser?

[jds]

Oh and sportster - was this the first time you tried it? I'm wondering if my update today changed things for you..

[sportster]

Oh and sportster - was this the first time you tried it? I'm wondering if my update today changed things for you..

First time I tried was when I posted about the ASP error.

[BobWang]

IE 8 returns this error:

Server Error in '/' Application.

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>

[jds]

IE 8 returns this error:

Server Error in '/' Application.

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>

Thanks - so ironic that MS' own browser won't take the ASP code properly, but FF will

[GonnaGetEm]

ah actually...



I wonder if that is giving some people an issue?

[sportster]

Typical MS crap. Then again our applications only run properly with iFrames and JQUERY using IE7.

[GonnaGetEm]

jds, it's working fine on my end.

What browser?

Firefox.

But I see you got the error there alright. I'm sure the one I posted is unrelated.

[problemchild]

Being newer to this credit thingy, can someone explain to me what B* and C* are and what exactly this application will do and why it will help? Sorry to be a pain in the #($, hope you all don't mind explaining this.

[sportster]

Does your opening SCRIPT tag use the TYPE attribute like this:

type="application/javascript"

IE doesn't support this if this is the case...

[jds]

Give it a shot in IE now. You might have to close your browser and go back in.

[sportster]

Works now! Nice job.

[jds]

Works now! Nice job.

Thanks!

GGE - The onload errors should be fixed in FF now, as well.

[GonnaGetEm]

Works now! Nice job.

Thanks!

GGE - The onload errors should be fixed in FF now, as well.

yup!

[jds]

Being newer to this credit thingy, can someone explain to me what B* and C* are and what exactly this application will do and why it will help? Sorry to be a pain in the #($, hope you all don't mind explaining this.

Long story short, B* is what happens when you get "too many" soft inquiries on your credit report (from checking your own credit). The result is that hard inquiries (the ones that can hurt your score) fall off sooner than normal.

C* is a process used by EQ to reduce the chances of this, by "chopping" all your soft inquiries down to one per month, making B* difficult.

There is a master thread on the first page of the credit form. Take a read through that, it will probably help explain.