# ProScan to PDF Compile Error

**URL:** <https://clarionhub.com/t/proscan-to-pdf-compile-error/6449>\
**Category:** questions\
**Tags:** compiler, pdf\
**Created:** [July 31, 2023, 8:38pm UTC](https://clarionhub.com/t/proscan-to-pdf-compile-error/6449 "2023-07-31T20:38:21Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![JRoman](https://clarionhub.com/letter_avatar_proxy/v4/letter/j/f05b48/32.png) [@JRoman](https://clarionhub.com/u/JRoman)\
**Post date:** [July 31, 2023, 8:38pm UTC](https://clarionhub.com/t/proscan-to-pdf-compile-error/6449/1 "2023-07-31T20:38:21Z")

</div>

Using Clarion 10.0.11975  
Lansrad Proscan 4.9

I get compile error on following code:

SelectInventorySold PROCEDURE

oHH &tagHTMLHelp  
oHH &tagHTMLHelp

The second entry for oHH &tagHTMLHelp is added after add button calling procedure WnScan2PDF.  
The WnScan2PDF is generated by the template.

Any advice on how to stop this?

Thanks! Glad I found this community.

---

<div class="post-metadata">

**Author:** ![anon51095673](https://clarionhub.com/letter_avatar_proxy/v4/letter/a/f9ae1b/32.png) [@anon51095673](https://clarionhub.com/u/anon51095673)\
**Post date:** [July 31, 2023, 9:50pm UTC](https://clarionhub.com/t/proscan-to-pdf-compile-error/6449/2 "2023-07-31T21:50:36Z")

</div>

support from… [LANSRAD Information](https://lansrad.com/html/about_us.html)

---

<div class="post-metadata">

**Author:** ![JRoman](https://clarionhub.com/letter_avatar_proxy/v4/letter/j/f05b48/32.png) [@JRoman](https://clarionhub.com/u/JRoman)\
**Post date:** [July 31, 2023, 10:30pm UTC](https://clarionhub.com/t/proscan-to-pdf-compile-error/6449/3 "2023-07-31T22:30:47Z")

</div>

Thanks for your reply! Submitted support web form 26/7. I emailed on 27/7. In the email I used subject “ProScan Help V4.9” to try to make it through any user side spam filters. Just thought I would reach out to the community in case it was a “no brainer” I was missing. Maybe the spam monster ate the message.

Also, if this should have been in a different area of the forum please correct me.

---

<div class="post-metadata">

**Author:** ![Bruce](https://clarionhub.com/letter_avatar_proxy/v4/letter/b/ccd318/32.png) [@Bruce](https://clarionhub.com/u/Bruce)\
**Post date:** [August 1, 2023, 3:50am UTC](https://clarionhub.com/t/proscan-to-pdf-compile-error/6449/4 "2023-08-01T03:50:04Z")

</div>

The error message is a clue to what is wrong.  
Post that do we can offer more explicit advice.

---

<div class="post-metadata">

**Author:** ![Graham\_Dawson](https://clarionhub.com/user_avatar/clarionhub.com/graham_dawson/32/1331_2.png) [@Graham\_Dawson](https://clarionhub.com/u/Graham_Dawson)\
**Post date:** [August 1, 2023, 9:06am UTC](https://clarionhub.com/t/proscan-to-pdf-compile-error/6449/5 "2023-08-01T09:06:30Z")

</div>

> [@JRoman](#):
>
> oHH &tagHTMLHelp

is a declaration added when you add the Clarion (or ABC) HTML Help extension to a procedure.  
If you have 2 of those then it’s possible you’ve added it twice, or maybe Globally and Locally?

---

<div class="post-metadata">

**Author:** ![Mark\_Sarson](https://clarionhub.com/user_avatar/clarionhub.com/mark_sarson/32/6132_2.png) [@Mark\_Sarson](https://clarionhub.com/u/Mark_Sarson)\
**Post date:** [August 1, 2023, 11:12am UTC](https://clarionhub.com/t/proscan-to-pdf-compile-error/6449/6 "2023-08-01T11:12:17Z")

</div>

This doubling up of code can also be caused when importing a procedure into an application if you are using a global template that inserts code into local procedures.

If this is the case you can edit the TXA file before importing into your application and remove the template addition.

If you look through the TXA for the procedure you will see sections that start with [ADDITION], look for any occurrence of the help template and remove them from the TXA, save and then import.

Mark

---

<div class="post-metadata">

**Author:** ![JRoman](https://clarionhub.com/letter_avatar_proxy/v4/letter/j/f05b48/32.png) [@JRoman](https://clarionhub.com/u/JRoman)\
**Post date:** [August 1, 2023, 5:06pm UTC](https://clarionhub.com/t/proscan-to-pdf-compile-error/6449/7 "2023-08-01T17:06:22Z")

</div>

The compile error is “No matching prototype” Clicking the error takes me to the clw highlighting the second instance of oHH &tagHTMLHelp.

---

<div class="post-metadata">

**Author:** ![JRoman](https://clarionhub.com/letter_avatar_proxy/v4/letter/j/f05b48/32.png) [@JRoman](https://clarionhub.com/u/JRoman)\
**Post date:** [August 1, 2023, 5:18pm UTC](https://clarionhub.com/t/proscan-to-pdf-compile-error/6449/8 "2023-08-01T17:18:59Z")

</div>

Mark, thank you for reminding me to check txa. Grateful for all of the feedback.

I should try and explain a bit better.

I select Application then Utility Template and import. At this point all is well. As soon as I add a button calling the imported procedure and compile I get the error. The second oHH entry is added to my update form procedure calling the imported scan to pdf procedure.

---

<div class="post-metadata">

**Author:** ![Bruce](https://clarionhub.com/letter_avatar_proxy/v4/letter/b/ccd318/32.png) [@Bruce](https://clarionhub.com/u/Bruce)\
**Post date:** [August 2, 2023, 2:29am UTC](https://clarionhub.com/t/proscan-to-pdf-compile-error/6449/9 "2023-08-02T02:29:07Z")

</div>

> > Clicking the error takes me to the clw highlighting the second instance of oHH &tagHTMLHelp

Does the place it takes you match the place reported in the errotd pad?

I expect a warning on the line you are going to, not an error. And not that error. I expect it has taken you to the first warning, not the position of the error.

---

<div class="post-metadata">

**Author:** ![JRoman](https://clarionhub.com/letter_avatar_proxy/v4/letter/j/f05b48/32.png) [@JRoman](https://clarionhub.com/u/JRoman)\
**Post date:** [August 2, 2023, 5:02pm UTC](https://clarionhub.com/t/proscan-to-pdf-compile-error/6449/10 "2023-08-02T17:02:07Z")

</div>

Ah, thank you Bruce. Your suspicion seems to be the case. The error may be on the button.

OF ?BUTTON2  
ThisWindow.Update()  
STA_RT(Wn_Scan2PDF, 25000)  
ThisWindow.Reset

I attempted to italicize the text highlighted in the error. It is the "RT(Wn "

I moved the Start command to the accepted embed of a new button and manually added it to the Calls for the procedure. However the error persists.

---

<div class="post-metadata">

**Author:** ![Mark\_Sarson](https://clarionhub.com/user_avatar/clarionhub.com/mark_sarson/32/6132_2.png) [@Mark\_Sarson](https://clarionhub.com/u/Mark_Sarson)\
**Post date:** [August 2, 2023, 5:24pm UTC](https://clarionhub.com/t/proscan-to-pdf-compile-error/6449/11 "2023-08-02T17:24:08Z")

</div>

Hi

At a guess, there are two possibilities.

1. WinScan2PDF is not in your application or defined anywhere.

If this is an issue, I would check the docs to make sure you have followed instructions on adding the 3rd Party to your application. I don’t know the product myself, but there may be a procedure you need  
to import, Utility Template you need to run etc.

If you have the procedure declared in another application, make sure you add that procedure as a module in this application to the module for the other application, if you need more help with that, shout.

1. WinScan2PDF takes extra parameters.

If the latter, START(…) can pass up to 3 STRINGS to the PROCEDURE who’s thread you are starting. From HELP for START, the 3rd - 5th parameter for start is described as:

> A string constant, variable, or expression containing the value to pass as a parameter to the procedure. There may be up to three passed values listed.

---

<div class="post-metadata">

**Author:** ![JRoman](https://clarionhub.com/letter_avatar_proxy/v4/letter/j/f05b48/32.png) [@JRoman](https://clarionhub.com/u/JRoman)\
**Post date:** [August 2, 2023, 8:43pm UTC](https://clarionhub.com/t/proscan-to-pdf-compile-error/6449/12 "2023-08-02T20:43:04Z")

</div>

Thanks everyone for your input. I found my problem.

When calling the procedure Start Thread must be unchecked. Or if calling from the accepted embed use the following WnScan2PDF(). I have yet to figure out the why. Although I am happy to have found problem, I dislike randomly trying things out of desperation. Is there a simple explanation so I can turn this in to a “learning moment”?

Thanks again!
