Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VM Pro 4.2 DB execute

Status
Not open for further replies.

as1981

IS-IT--Management
Joined
Sep 28, 2006
Messages
394
Location
GB
All,

I have an execute statement following a database open statement which sometimes works and sometimes fails with the same user inputs.

The system e-mails me the user inputs when the execute fails and when I try it works fine.

Is there any way to obtain the failure reason?

Does anyone have any other thoughts or seen the same before?

I can upload the module as text if that would help.

Thanks

Andrew
 
Sorry one thing to add. There is a seperate e-mail notification if it fails to open the DB connection so I know it's the execute that's causing the problem.
 
You need to check the SQL query to make sure it is 100% on the nose.

You could use the VM Debug app to have a look at what happened to the failed calls

Jamie Green

Football is not a matter of life and death-It is far more important!!!!
 
Thanks for the reply. If the SQL statement was faulty then it wouldn't intermittently work with the same inputs?

By VM debug app do you mean running the live VM in some kind of debug mode (I'll research how to do it) or a separate app?

Thanks

Andrew
 
Thanks for the link. I'm running the program on the VM server with all the capture options set but nothing is appearing in the log window.

Does the VM pro need to be started in debug mode so that it creates the debug output? If so can I run a live VM in debug mode?
 
Sorry ignore the last post. It's started now.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top