I mean the environment running the executable you created which results in the error. Are you working with environment variables within the code? Posting a short example which recreates the issue would be advantageous.

"Is the fact the executable does run without error highlight that perhaps the perl is ok, and as you say more of a systems issue?"

This statement has confused me. I thought your report was that the executable did spit out an error at the prompt?

"one thing I did try in order to eliminate some possibilites is to create a .exe to run as an icon from a windows environment"

I think your efforts would be better spent isolating the problem in the current environment.

My apologies for the confusion. I simply meant that running the perl script independantly works fine. Running the executable also 'works' but displays in an undesirable way due the the : not an identifier message.

FOR EXAMPLE: when I run my program it clears the gui window down, and displays username and password in the centre in order for the user to input details. - However when running the executable, the screen is cleared, but the user name is right at the bottom of the screen, with the :not an identifier just above it, and the same stands for when the user has input correct details, the main menu is all messed up because the : not an identifier is printed to screen and shifts everything down.

Its almost like 'something' is getting stored in some kind of buffer. Hopefully i explain this bit right - I changed the executable name and now the last letter on the command line is before the error like: e: is not and identifier, which is almost like it's being left behind asfter pressing 'return' to run the script - does that sound plausable?

Without a script to replicate the problem anything I tell you from here on in is conjecture. For example, you may experience weirdness if you're running system commands in an environment which has problems.

From experience it's best that we don't draw this out piecemeal. Don't introduce new factors to the equation (e.g. MS Windows build), stick with the facts and provide an example which anyone can run to try and recreate the issue in question. I say 'try' because if this problem relates to an issue with your environment you will need to debug the issue further. For clarity, on the target system running the packaged version throws an error, running the normal version does not? My advice for your next post would be to include the example code discussed and details of the environment you're running this in.