- Local time
- Yesterday, 19:15
- Joined
- Feb 28, 2001
- Messages
- 31,044
Dave, you will eventually realize that asking for help in a medium where folks cannot see what you are doing is essentially asking a blind man to describe the Mona Lisa - and then improve on it. What you get might look like Salvador Dali on one of his not so good days. Or like something my youngest grandson would draw. (He's 2 years old next month.)
So... let's talk CSV files and what can go wrong.
First, if you export a .CSV file, you had better not have commas embedded in the file UNLESS you have also set the option to export text content in quotes. Can you assure us that you have set that option where appropriate? If not, there's your misalignment right there.
Second, if you import a .CSV file, you merely make the ASSUMPTION that the commas will guide the import. But that is a sometimes incorrect assumption depending on other import options. .CSV imports don't occur in a vacuum.
Third, I'm not sure whether hard <TAB> characters can screw up a CSV import, but it has been known to screw up other imports. Got any of those in the mix?
Fourth, your attitude of "don't ask me questions, just give me answers" is exactly what tends to get your sorry attitude put on an ignore list.
Fifth, this is the most PRESUMPTUOUS statement ever made on this forum:
You are talking to a group with a collective 50+ years of experience just in the folks who answered you, not counting any other viewers. Two of us are Microsoft MVPs for Access. I'm not sure whether you know what that means, but I'll tell you what it doesn't mean... It means we aren't stupid and we don't often answer without knowing what we are doing. And Microsoft Corporation doesn't hand out MVP awards for grins and giggles.
You might well be right about "the right way" to do something. But working blind in this particular medium makes it nigh unto IMPOSSIBLE to determine that fact. So saying it doesn't make it obvious to us.
Oh, as to changing proprietary code? If you are having trouble, go to the dork who sold you that pile of dyspeptic dragon droppings in the first place. Or did you so badly tick that person off with your uncooperative attitude already that s/he won't talk to you?
You are right about not wanting to change proprietary code. But then, if it is the part that is broken, are you willing to live with it as-is?
So... let's talk CSV files and what can go wrong.
First, if you export a .CSV file, you had better not have commas embedded in the file UNLESS you have also set the option to export text content in quotes. Can you assure us that you have set that option where appropriate? If not, there's your misalignment right there.
Second, if you import a .CSV file, you merely make the ASSUMPTION that the commas will guide the import. But that is a sometimes incorrect assumption depending on other import options. .CSV imports don't occur in a vacuum.
Third, I'm not sure whether hard <TAB> characters can screw up a CSV import, but it has been known to screw up other imports. Got any of those in the mix?
Fourth, your attitude of "don't ask me questions, just give me answers" is exactly what tends to get your sorry attitude put on an ignore list.
Fifth, this is the most PRESUMPTUOUS statement ever made on this forum:
You are talking to a group with a collective 50+ years of experience just in the folks who answered you, not counting any other viewers. Two of us are Microsoft MVPs for Access. I'm not sure whether you know what that means, but I'll tell you what it doesn't mean... It means we aren't stupid and we don't often answer without knowing what we are doing. And Microsoft Corporation doesn't hand out MVP awards for grins and giggles.
You might well be right about "the right way" to do something. But working blind in this particular medium makes it nigh unto IMPOSSIBLE to determine that fact. So saying it doesn't make it obvious to us.
Oh, as to changing proprietary code? If you are having trouble, go to the dork who sold you that pile of dyspeptic dragon droppings in the first place. Or did you so badly tick that person off with your uncooperative attitude already that s/he won't talk to you?
You are right about not wanting to change proprietary code. But then, if it is the part that is broken, are you willing to live with it as-is?
