Agony

107 reputation

bio	website
	location
	age
visits	member for	10 months
	seen	Dec 3 '12 at 10:44
stats	profile views	9

	107 reputation	bio	website		visits	member for	10 months
5 badges		location			seen	Dec 3 '12 at 10:44

summary answers questions tags badges favorites bounties reputation activity

43 Actions

suggestions reviews revisions comments badges posts accepts all

Sep 5	comment	SELECT value from database over ODBC wont reach the software Is there any kind of "buffer"or 2rd party storing etc in between SQL DB and odbc
Sep 4	revised	SELECT value from database over ODBC wont reach the software New updated info.
Aug 31	comment	SELECT value from database over ODBC wont reach the software I dont have access to the software sourcecode so i cant post the query it uses, except what it shows in the log above. It works with clan database and compared to it, when problem started, there wasn't that many new entries added. the hsmt error above occurs only when it selects from that table, manually selecting from it works fine. And there isnt that many rows in there - when it started, there was like 2-3 rows. I wish i could trace/log what "result" it was that kept it busy. The table has no dependencies listed nether that could mess with it.
Aug 30	comment	hStmt/cursor error caused by faulty data? its over odbc. The software problem was eliminated by testing it with original database, also by using clean copy of the software and it runs fine for others who use the same file. It is over sql server driver (the native isn't fully supported by the developer). Its something that has worked fine for years, yet just suddenly failed. The database itself has not been changed and server software ether uses procedures or queries to read/write/select data, but makes no changes to the tables or creates them.
Aug 30	comment	hStmt/cursor error caused by faulty data? for this one it was the tblguild issue, now its related to a tbl general with focused on the hsmt error. The previous one, for a unknown reason vanished by itself.
Aug 30	asked	hStmt/cursor error caused by faulty data?
Aug 26	accepted	xp_cmdshell bcp wont save file
Aug 25	asked	xp_cmdshell bcp wont save file
Aug 24	comment	SQL Server and updating windows firewall rules yeh the firewall cmd line part isnt a problem, im just wondering how do i get access to them, powershell would work too i guess. xp_cmdshell - but can i pass a value to it from SELECT ?
Aug 24	asked	SQL Server and updating windows firewall rules
Aug 24	accepted	SQL Server trigger (update or insert with inner join problem)
Aug 24	comment	SQL Server trigger (update or insert with inner join problem) that should do indeed, i simply added IF (UPDATE([Kill])) BEGIN to limit the trigger from doing extra unneeded work and only run it if the KILL was actually updated (not when some other column got updated in the table).
Aug 24	comment	SQL Server trigger (update or insert with inner join problem) ok but now that eliminates the primary key violation issue, however it wont update the killer table if the serial already exists.
Aug 24	revised	SQL Server trigger (update or insert with inner join problem) edited title
Aug 24	comment	SQL Server trigger (update or insert with inner join problem) the one above seems to insert only if ON i.serial = k.serial; but that woudl end up wit ha error since i cant enter duplicate primary keys. So i need it to insert a new one if it doesnt exist and update if it does exist.
Aug 24	comment	SQL Server trigger (update or insert with inner join problem) The trigger works - however due to the primary key, i cant insert duplicates so i need to update if it already exists. But im not sure how to set up the UPDATE [Kill] WHERE serial = xxxx - i cant use i.serial here (a multi-part error)
Aug 24	comment	SQL Server trigger (update or insert with inner join problem) the problem with my trigger above is that it will only insert - however i need a "exist" check first and update if a serial in the table its writing to, exists already (the serial in killer table is a primary key).
Aug 24	awarded	Commentator
Aug 24	comment	SQL Server trigger (update or insert with inner join problem) then i woudl still have to compare the values it wants to enter with existign ones, so my trigger would run only if specific column gets updated IF (UPDATE([Kill]))
Aug 24	comment	SQL Server trigger (update or insert with inner join problem) inserted and deleted are sql special tables not real tables in my db (stores deleted and insert values before query is actually run or something like that).