Viewing 15 posts - 52,936 through 52,950 (of 59,091 total)
Perfect... thanks for taking the time to post your feedback!
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 4:16 pm
Thanks for the feedback, Chris... glad it helped.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 4:07 pm
The Nirvana that you hint about. This is only likely to exist when all IT systems are in a constant state of renewel, and there is no legacy to deal...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 4:02 pm
Heh... worse... RBAR on steriods over the "pipe".
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 5:57 am
Heh... lemme say it again...
The user that the SQL Service logs in as, must have permission to "see" the share.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 5:54 am
Heh... thanks... good to know.
And, my bad... didn't look at the first post... this is Oracle code...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 5:49 am
Because in a proper mixed format fixed field data set, each row will have a "rowtype" marker. Mixing header information in the data will frequently cause bulk loads to...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 5:46 am
Sure, Praveen... I just said that 😉 but thanks for the feedback.
And, my bad... Ramesh was the one that said it needed to be done without a temp table and...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 5:34 am
Adrian is correct,
Anything that looks like a numeric entry, will be treated like one by Excel. If you type 000123 into Excel, it will be changed to 123 by...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 5:27 am
One might also try posting the original question on an Access forum... I do very little in Access and don't know the answer other than running the script you originally...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 5:12 am
I guess I don't understand... why does the addition of columns to tables in ACCESS have to be automated to begin with?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 5:10 am
If we had found a solution for you, everyone would benefit because we would post the answer. To be courteous, you should too...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2008 at 8:08 pm
You must create a scheduled job that logs into the FTP site and checks to see if the file exists usining FTP directory commands.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2008 at 8:07 pm
You cannot output columns that are not in the GROUP BY unless they are in an aggregate function... read Books Online for the proper use of GROUP BY.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2008 at 8:04 pm
I strongly suspect that the only mod that has been done is the number of rows have increased. 2.5 million rows is right at the threshold of the "tipping...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2008 at 7:58 pm
Viewing 15 posts - 52,936 through 52,950 (of 59,091 total)