Viewing 15 posts - 76 through 90 (of 363 total)
Man it goes down hill fast when posts are shorter than "short stories" ![]()
Once you understand the BITs, all the pieces come together ![]()
January 30, 2004 at 8:56 am
Oops, Sorry David
, I was thinking of you while writing... never got to it because the thought of "timing out on post submit"...
Once you understand the BITs, all the pieces come together ![]()
January 30, 2004 at 7:30 am
Bill, I'm glad we all could help, even if we like to get off topic once in a while. Usually Frank's replies are right on the mark and helpfull. They will...
Once you understand the BITs, all the pieces come together ![]()
January 30, 2004 at 7:09 am
Mike,
It sure seems that way "explicit commit (inside the OpenRowSet)"... Seems very strange to me if this IS the case???? Still doen't explain why I get the same kind...
Once you understand the BITs, all the pieces come together ![]()
January 30, 2004 at 6:55 am
Shoot, I was writing a nice reply post, and lost it (timeout maybe??)
I get the same symptom on many of the servers here.
I use Q/A and either login as...
Once you understand the BITs, all the pieces come together ![]()
January 29, 2004 at 2:56 pm
>> Does this make any sense?
Maybe a little
...
I do not see the "property date", you mention, in the SELECT statement you provided???...
Once you understand the BITs, all the pieces come together ![]()
January 29, 2004 at 11:30 am
So there is not way of getting a "return value" of the IDENTITY from the Winsock call you have to make. Right?
When you make the Winsock call, and it procedes...
Once you understand the BITs, all the pieces come together ![]()
January 29, 2004 at 11:02 am
Can you post, or Private Message me, the 1st few records of your file? May 1st 100 lines or so.
Make sure what you post produces a error/problem on your end...
Once you understand the BITs, all the pieces come together ![]()
January 29, 2004 at 9:38 am
I do the same sort of thing with back end produced text files, each file containing multiple tables.
1. Get each import table's data into #Temp tables in the fastest way...
Once you understand the BITs, all the pieces come together ![]()
January 29, 2004 at 9:21 am
Instead of
table1.name LIKE '%[table2.name]%'
Try
table1.name LIKE '%' + [table2.name] + '%'
Or optionally
table1.name LIKE '%' + RTRIM([table2.name]) + '%'
Once you understand the BITs, all the pieces come together ![]()
January 29, 2004 at 9:01 am
Thanks, I have to leave in a couple min., ....
How do I pass a blob > 8K as a parameter to SP?...
Once you understand the BITs, all the pieces come together ![]()
January 28, 2004 at 4:48 pm
Allen, maybe instead of "VB Executing" your INSERT, call the "insert" in the form of a "record set" query returning your identity to be used as a constant in subsequent...
Once you understand the BITs, all the pieces come together ![]()
January 28, 2004 at 4:09 pm
Check out row 15 (or 14,16
) of your raw data for maybe a missing comma, or invalid QTY value.
I just cut & pasted...
Once you understand the BITs, all the pieces come together ![]()
January 28, 2004 at 4:02 pm
Then I think Frank's idea of having 1 table hold results for multiple report requests is a solution. Otherwise, yout would have to make a unique named table, either permanent...
Once you understand the BITs, all the pieces come together ![]()
January 28, 2004 at 3:48 pm
Will this little snipet help?:
Create Table Test1 (ID int IDENTITY (1, 1), Data1 varchar(10))
Create Table Test2 (ID2 int, Data2 varchar(10))
Insert Into Test1 (Data1) Select 'Data for 1'
Insert into...
Once you understand the BITs, all the pieces come together ![]()
January 28, 2004 at 3:38 pm
Viewing 15 posts - 76 through 90 (of 363 total)