chr$(34)

[ashishrajvanshi]

Hello All,

I have written a piece of code with the following line being used for quotes

strQuote = Chr$(34)

It is working fine on my computer however, when the file is run on another computer, it gives a compiler error that the library is not found and highlights the above line.

Do we need any additional library to execute the above code.

Thanks and Regards

[TheBionicOrange]

Try :

strQuote = Chr(34)

[ganeshmoorthy]

check you references thru Project -> References and see whether any thing got highlighted there...

[Al42]

however, when the file is run on another computer

It's never a good idea to just copy a VB .exe file to another computer. Make a package and install the program on the other computer. It's possible that the needed library was never installed on the other computer, or the file got damaged.

[brian.sykes]

If they dont have the VB6 runtimes it wont work very well at all.

[sigid]

...another idea is to declare a CONST such as CONST Q = """" (that's 4 double quotes in a row).

But ganeshmoorthy is correct - if any intrinsic function yields the message about library not found, the project has a reference on one machine that does not exist on the other...

[MartinLiss]

You will run into many problems if you don't actually install your app on other PCs. To do that you create a set of installation file using the P&D Wizard that comes with VB, Inno or some other 3rd-party installer.

I've also moved your thread to this forum.

[RhinoBull]

Hello All,

I have written a piece of code with the following line being used for quotes

strQuote = Chr$(34)

It is working fine on my computer however, when the file is run on another computer, it gives a compiler error that the library is not found and highlights the above line...

Thread rather "belongs" to VB.Classic forum...

Anyway, for unknown reason VB6 may lose references to VBA library although it still appears in the list of project's references. You can do either:

- recreate your project by create a brand new and addid all objects from the existing and then save new by overwriting the old one.
- or add VBA namespace in front of the "offensive" functions:

VBA.Left$
VBA.Chr$()
etc...

If there are too many occurences then you can utilize Find/Replace With functionality:

search for Chr$ and replace it with VBA.Chr$ ...