RE: Changing LoadRunner/VuGen log options at runtime

I found (several versions ago) that writing logging statements gave different and often undesirable results, depending on the start position of logging – particularly if I switched to log on error (my default). I often like to switch extended logging on to record a specific (e.g. an order number). The code below relies on your log level table but always works.

int rc;

rc=lr_get_debug_message();
lr_set_debug_message(rc, LR_SWITCH_OFF);
lr_set_debug_message(18, LR_SWITCH_ON);
lr_log_message(“***** Order Number: %s”, lr_eval_string(“{cOrdNo}”));
lr_set_debug_message(18, LR_SWITCH_OFF);
lr_set_debug_message(rc, LR_SWITCH_ON);

Thank you for your nice article. I found something special on it.
Thanks

I have a functionlibrary in vbscript developed in QTP for oracle forms login with 16 instances.Each instance has it’s own id and password.Now I want to reuse it with LoadRunner.
I have the following options:
1.Convert VBscript Function library to C userdefined function library for LoadRunner

2. Using VBscript as the language in LoadRunner to reuse the scripts developed in QTP directly.

3. Develop new C function library (I am a bit afraid to invest time here to do the same task again,So not considering this option

Could you please give me tips on using VBscript as the language in LoadRunner to record

or

how to use efficiently the QTP Script developed in LoadRunner

or code conversion from VBscript to C language

Thanks
Suresh