I do like your project "pausep".
But I would like to get a version of it able in working under Win95/98.
I have browse all the web with no success.
Maybe you may help me?
my private email is: [DELETED]@gmail.com, please be so kind also to tell me you may not help me.
Maurizio Dan Revella from Italy
Plus, two things:
1) Post your reply to the right message, or the notification will never reach the recipient, and you will only get a response if they happen to notice it. Replying automatically sends an email to the registered email address, so it should be quicker and more efficient.
2) Don't post in a users forum, if it relates to a specific article - each article has a message forum at the bottom which allows discussion specific to that article (and it enables all relevant correspondence to be kept together).
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
I still use ASM, I program micro-controllers and EEPROM chips. Ok ok, this is almost pure hardware. But as you can see, there's still use for ASM code in this modern world. Even your washing machine or microwave still relies on this pretty basic language
Hi, I read your article about SQL Server DO's and DONT's, it is pretty usefull for me because I don't know much about sql server performance stuff. Actually I have a question to ask, I am developing an application and I got stucked with some stuff with sql server stored procedures, and since you seem to know a lot about databases maybe you could give me a hand with this.
The thing is, I have this stored procedure which calls another stored procedure to get a result set and do some stuff with the data. The second stored procedure is located in some other database inside the server. I need to call this stored procedure, and if it fails to get the data or the connection fails with the database then I have to execute some other instruction in the first stored procedure and return a result set from another table without letting the user know that the stord procedure failed in some point of the execution.
Is there a way that I can implement something like a try catch in sql server 2000. I don't really care about catching the error thrown by the stored procedure, but continue with the execution of the secondary instructions. actually I have something like this but it doesn't works
CREATE PROCEDURE GET_INFO
declare @err as int
EXEC TCR..Get_Order @OrderID
SELECT @err = @@Error
IF @err <> 0
OrderNum = @OrderID
Any help would be greatly appreciated, even if the answer is that what I need to do is not possible with this version of sql server.
If you dislike vb.net that much Why did u even switch to .net platform or is it because your java c c++ days are numbered?
I do not believe you can get all .net and its framework has to offer unless you code in vb.net plain and simple expecialy on Asp.
Your c# is too case sensitive,boring, and abnormal and you all outsider should be lucky Microsoft let you into its new studio.
Gone are the days when no one know which comment end what which only slow things down
Welcome to the new world where high speed coding rules.
And No! am not converting my code to c# and we end get paid less at least we are less miserable.
Last Visit: 21-Feb-19 20:35 Last Update: 21-Feb-19 20:35