15,909,539 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View Python questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by vb_buddy (Top 4 by date)
vb_buddy
27-Aug-18 1:16am
View
thank you... will scrutinise the SP
vb_buddy
23-Aug-18 3:34am
View
U are true... this might not solve the problem...
I will explain you the process of transaction :
The software runs on VB.net
-> the user clicks on the save button
-> it goes to a function and gives all the data viz.. name of the stored procedure, columns names, raw data through command.Parameters.AddWithValue
and than the whole set of queries is executed in the stored procedure.
And than it again comes back to vb.net and takes the result. In case if anything goes wrong in between, the entire transaction is rolled back and throws an error through VB.Net.
My idea is if this whole set of transaction takes more than a specified amount of time, it should not be executed and should throw an error to the user. And than the user has to again process the transaction.
I have a gut feeling that you will solve my problem.
Warm Regards..
vb_buddy
23-Aug-18 3:08am
View
Thank you... will try
vb_buddy
21-Aug-18 7:53am
View
Thank you all for your valuable time for my query.
Can we put timeout value for queries in stored procedure.
say 10 seconds, and if it crosses the time, the entire transaction is rolled back.
Thanks in advance