Error Compiling with Include File

sonny

for the last two versions of Netlinx Studio I have gotten the following error, when building the workspace, when using an include file that was created with "Add New Include File"

ERROR: some_directory\MainModule.axs(1)NetLinx Pre-Processor Error: Unrecognized char in input
ERROR: some_directory\MainModule.axs(1)NetLinx Pre-Processor Error: Unrecognized char in input
ERROR: some_directory\MainModule.axs(1)NetLinx Pre-Processor Error: Unrecognized char in input
some_directory\MainModule.axs - 3 error(s), 0 warning(s)

I can create the inital stub of the include file in Notepad, then "Add Existing Include File", without an issue. This has only happened in the last version of 2.4 and in 2.5. I called tech support but got "sorry, you're using XP Home, we can't help you".

Anyone else seen this issue? I really have a huge time believing it's related to XP Home.

Thanks...

NMarkRoberts

I have seen that error many times. It has nothing to do with how you create an include file or what OS you are using.

It is demonstrably caused by an editor bug (which I have not been able to pin down) because it happens spontaneously during an editing session. An invisible bad character is somehow present in your code.

It is easy to fix.

Start with the first error. Double-click on the error message to take you to the approximate location of the bad character. Delete a couple of lines of code each side of the location. Recompile to confirm that you have removed the dud character. Now type the lines back in - don't try to re-paste as the dud character will reappear.

DHawthorne

sonny wrote:

I called tech support but got "sorry, you're using XP Home, we can't help you".

Anyone else seen this issue? I really have a huge time believing it's related to XP Home.

Thanks...

That kind of response really annoys me. It's a cop out; I hope you got that tech's name. They should at the very least help you isolate the problem to confirm it's an OS issue if they suspect that, not just brush you off. I remember similar issues before Phast was purchased by AMX, and they told me my problem was I upgraded from Windows ME to 98. My feeling is that when a new OS comes out, developers are under an obligation to port any current product to it; it's unreasonable to expect your dealers to not upgrade thheir systems because you are holding back. And you can't even say that much about XP Home - it's not only a current OS< it's been around quite a long time.

[Deleted User]

If you are still having problems, make sure you have the "Enable UTF-8 format to display Hebrew, Arabic, Cyrillic and Han Characters" option unchecked before you create a new include file. This option is located on the "Editor" tab of the Preferences dialog.