Seems simple - can't solve the problem

[Guest]

I have a relatively straightforward dll, written in VB.net, that will not run
properly on a Vista box. Not sure this is a vb.net issue, but I have covered
every secutiry possibility (at least I think I have) and I thought I'd start
here.

The process is this:

We pass
1) an ID for a person in our database, and
2) an ID for an RTF format document (a standard form of some kind) to an ASP
page as follows:

forms_print.asp?custID=7004&formID=175

This RTF document has specially denoted fields on it, e.g. <<LastName>> that
are to be replaced with data from the DB.

The ASP page
1) gets the data pertaining to the person from our DB as an XML document and,
2) calls the dll to do a "text replace", i.e. replace <<LastName>> with the
actual last name of the person, then
3) opens the RTF document in Word or Word Viewer for printing or whatever
the user wishes.

This process works flawlessly under XP, but wont work under Vista. We have
reviewed permissions, etc. and just dont know where to start to solve this
problem.

Does the dll need to be rebuilt on a Vista machine or with some other
reference we aren't aware of?

Any guidance appreciated.

 

[Tom Shelton]

I have a relatively straightforward dll, written in VB.net, that will not run
properly on a Vista box. Not sure this is a vb.net issue, but I have covered
every secutiry possibility (at least I think I have) and I thought I'd start
here.

The process is this:

We pass
1) an ID for a person in our database, and
2) an ID for an RTF format document (a standard form of some kind) to an ASP
page as follows:

forms_print.asp?custID=7004&formID=175

This RTF document has specially denoted fields on it, e.g. <<LastName>> that
are to be replaced with data from the DB.

The ASP page
1) gets the data pertaining to the person from our DB as an XML document and,
2) calls the dll to do a "text replace", i.e. replace <<LastName>> with the
actual last name of the person, then
3) opens the RTF document in Word or Word Viewer for printing or whatever
the user wishes.

This process works flawlessly under XP, but wont work under Vista. We have
reviewed permissions, etc. and just dont know where to start to solve this
problem.

Does the dll need to be rebuilt on a Vista machine or with some other
reference we aren't aware of?

Any guidance appreciated.

What exactly doesn't work? Do you get an error of some kind? If so,
what does it say?

 

[Guest]

Yes, I guess this information would help - sorry about that.

On a Vista box the process get to the points where the dll should be
instantiated, the text replaced, and the document opened but this never
happens. I have written extensive debugging capabilities into the process so
if the process was actually kicked off I would see something in debug mode
(e.g. DB values searched for and found, etc.) but I get nothing returned to
me.

Other info that may be helpful: The app that is kicking off this process is
a locally running ASP based app.

Thanks!

 

[Guest]

Also, as a follow up:

Through basically "blind tweaking" we have now gotten this to the point
where Word (2007 in this case) will open but no text is displayed. In debug
mode, where I essentially response.write to the screen any text replace that
is done, I still get no indication at all of what the issue might be.

 

[rowe_newsgroups]

Yes, I guess this information would help - sorry about that.

On a Vista box the process get to the points where the dll should be
instantiated, the text replaced, and the document opened but this never
happens. I have written extensive debugging capabilities into the process so
if the process was actually kicked off I would see something in debug mode
(e.g. DB values searched for and found, etc.) but I get nothing returned to
me.

Other info that may be helpful: The app that is kicking off this process is
a locally running ASP based app.

Thanks!

What exactly doesn't work? Do you get an error of some kind? If so,
what does it say?

Sounds to me you have an ASP problem then and not a Visual Basic
(or .Net for that matter) problem. I don't know much about classic
ASP, so my only advice is to refer you to the ASP newsgroup. I believe
it is microsoft.public.inetserver.asp.general but I could be mistaken.

Thanks,

Seth Rowe

 

[Guest]

I'll try there as well. Thanks for your reply.

Yes, I guess this information would help - sorry about that.

On a Vista box the process get to the points where the dll should be
instantiated, the text replaced, and the document opened but this never
happens. I have written extensive debugging capabilities into the process so
if the process was actually kicked off I would see something in debug mode
(e.g. DB values searched for and found, etc.) but I get nothing returned to
me.

Other info that may be helpful: The app that is kicking off this process is
a locally running ASP based app.

Thanks!

I have a relatively straightforward dll, written in VB.net, that will not run
properly on a Vista box. Not sure this is a vb.net issue, but I have covered
every secutiry possibility (at least I think I have) and I thought I'd start
here.

The process is this:

We pass
1) an ID for a person in our database, and
2) an ID for an RTF format document (a standard form of some kind) to an ASP
page as follows:

This RTF document has specially denoted fields on it, e.g. <<LastName>> that
are to be replaced with data from the DB.

The ASP page
1) gets the data pertaining to the person from our DB as an XML document and,
2) calls the dll to do a "text replace", i.e. replace <<LastName>> with the
actual last name of the person, then
3) opens the RTF document in Word or Word Viewer for printing or whatever
the user wishes.

This process works flawlessly under XP, but wont work under Vista. We have
reviewed permissions, etc. and just dont know where to start to solve this
problem.

Does the dll need to be rebuilt on a Vista machine or with some other
reference we aren't aware of?

Any guidance appreciated.

What exactly doesn't work? Do you get an error of some kind? If so,
what does it say?

Sounds to me you have an ASP problem then and not a Visual Basic
(or .Net for that matter) problem. I don't know much about classic
ASP, so my only advice is to refer you to the ASP newsgroup. I believe
it is microsoft.public.inetserver.asp.general but I could be mistaken.

Thanks,

Seth Rowe