test
Files in globals.h are assumed to be there to support the compile of the script. Placing a file name there does Not automatically include it with the script when downloaded to a different load generator. So it might compile in VUgen but fail when directed to another load generator.

If you are using a local file that is on the same system as the vugen is going to compile against, ie myspecials.h, you would use the ''#include filename'' or #include ''myspecials.h''.

If the file is in the search path, you put the name in double quotes, like you see in globals.h for, say, a web script.

#include ''lrun.h''

You can also hard code a path like

#include ''C:Program Files (x86)HpLoadRunnerincludelrun.h''

Surprisingly, a UNC to a share also works, or at least compiles :)

#include ''\localhostC$Program Files (x86)HpLoadRunnerincludelrun.h''

Your best bet is to copy your file where LR Vuser compiles already look. That can be the load runner include directory, or the script's directory where the action.c resides (or vuser_end.c or vuser_init.c). That is also in the search path for the compiler.

Best bet is to include it in the script directory where the action.c, vuser_init and vuser_end reside. That is where the ''additional files'' comes in (v11.5x and v12.x). In earlier versions you would do it through the scenario that would allow you to specify additional files.
''Additional files'' is also good for keeping other types of files in the script itself and accessing them through C functions like fopen, fscanf, fread, etc. By default, when you open a filename without path info, it opens the file in the script directory.

Hope that helps. Good luck.

Not totally sure what you are asking, but you can add text files or any other files by right clicking on the extra files folder and browsing to the file and adding it. The file will then stay with the script.