Hi Steve, Try to be sure that IDL Path contains the token . If that token is not included in the IDL path, then IDL will not be able to find its own routines and functions. You can check that from the Workbench if you go to: Window --> Preferences --> IDL --> click in the (+), then click in Paths. If it's missing, click in the button to the right to Insert Default. Cheers, fernando

I should have pointed out, I am on a Linux system not Windows. It doesn't even appear that I have an IDL_PATH set. -Steve

So the path itself was OK, which I figured since this was the only function that didn't seem to work properly. The problem ended up being an older routine in a subdirectory with the same name "colorbar.pro". The issue now is that the location of the default IDL library has many other directories with additional libraries in them. Is there a way to exclude a subdirectory from the IDL_PATH or do I have to list all the ones I do want IDL to search through separately? I would just rename/delete the file but I am not the only one accessing these routines. -Steve

Hi Steve, Well, I don't think will be a good idea to exclude IDL subdirectories from the IDL_PATH. Specially because IDL will not work well if you don't have that token () and the token contains many directories that are necessary for IDL to work correctly. What you really need to do is to re-name the user's define routines so that they don't conflict with IDL routines' names. That will be the best practice. cheers, fernando