Viewing 15 posts - 12,421 through 12,435 (of 18,923 total)
It's like asking a mechanic to fix your flat tire without bringing the car in. That's just not gonna work.
October 24, 2005 at 1:34 pm
Mine too since she didn't use the correct join syntaxe everytime she posted but that's another story.
October 24, 2005 at 1:19 pm
The same still applies.
Post :
- Table definitions
- sample data
- wrong resultset
- expected resultset
October 24, 2005 at 1:15 pm
Had already forgot about that "great uproar" thread
.
October 24, 2005 at 1:03 pm
This in a non-smoking buidling??? They'll get your head for this, you'd better stop right now
.
October 24, 2005 at 12:48 pm
She doesn't have that killer instinct... I wouldn't worry too much about it if I were me
.
October 24, 2005 at 12:41 pm
Don't remember who said that but : You're always right when I'm not wrong
.
Still fumigating on that guess?
October 24, 2005 at 12:38 pm
I see. I've never faced that problem and I can't think of a solution at the moment... maybe someone else will be in a better position to help you.
October 24, 2005 at 12:36 pm
Sorry mick, I missed the part where you said read before posting the question. I shouldn't have gone off like that.
Here are the passages you missed :
October 24, 2005 at 12:12 pm
Does this have to be run as an SP or can the code be fired from another application?
October 24, 2005 at 12:10 pm
You can delete the post using the edit button / delete
October 24, 2005 at 12:08 pm
Maybe one fo the possible causes... Access will try todo the most work it can on the sql server, but at some point, more than necessary data will be sent...
October 24, 2005 at 11:23 am
Viewing 15 posts - 12,421 through 12,435 (of 18,923 total)