Re: Importing .dat file

I wouldn't pay you $200/hour if you were the only person in
the universe who had a piece of information that I needed. And
I wouldn't trust you within 10 feet of any of my projects,
or within a mile of any of my clients.

You've obviously never written software for a bunch of clients
in a corporate environment, or you would know that *you* do the
back-end SQLServer stuff, and it should be invisible to the client.
It is not the primary responsibility of my users to do SQLServer.
They want an application that helps them do their actual job,
not one that requires them to learn more technology that they
don't care about.

Robin S.
-----------------------------------------------


<aaron.kempf@xxxxxxxxx> wrote in message
news:1169681204.184297.206100@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
SQL Server is _NOT_ that complex, Robin

maybe you should grow some BALLS and stop being scared of it

if you want my help; I charge $200/hour for the first hour and $150
after that.

seriously-- SQL Server is _NOT_ that complex; if these stupid dipshits
would stop using Excel for everything and start using a database; they
might know how to do it themselves

and it's pointless-- I can push it into Thunderbird if it has ODBC; I
mean SQL Server Developers' edition costs $49; it's super easy

if thunderbird doesn't have ODBC then it's not a real database

-Aaron

On Jan 24, 11:27 am, "RobinS" <Rob...@xxxxxxxxxxxxxxx> wrote:
In addition to Bruce's right-on comments, this also doesn't
take into account that it might be something the OP wants
to run over and over again, or give to a user to run, and
a user will just want to press a button.

I would rather tear out my fingernails than try to teach
one of my corporate users to open and use SQLServer, let
alone deal with the aftermath after they accidentally delete
the database. Plus, did I mention they'd rather just press
a button? Isn't that one of the basic reasons for software
development -- to make things easier for the users?

Robin S.
----------------------------------
"Bruce W. Darby" <kraco...@xxxxxxxxxxxxx> wrote in
messagenews:CuadnRC3YoSORCvYnZ2dnUVZ_umlnZ2d@xxxxxxxxxxxxxx

<aaron.ke...@xxxxxxxxx> wrote in message
news:1169608773.127471.174640@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
right click IMPORT fucknut

I'm going to assume that you are using the trailing adjective to
describe your feelings for me, so I won't comment on that one. :)
But
where would I right-click IMPORT? Which program? Or are you telling
me
that you don't WRITE code, you just use the tools that someone else
has coded to do your work?

or File, open, files of type = DAT probably in Excel LoL

"Probably" in Excel? You aren't sure?

or rename the extension to TXT and use 'text to columns' in excel

And what happens if his data is encrypted? Many .dat files are, ya
know. How would he save it as a .txt file and then expect Excel to
know how to decrypt it? Another note.... if the file ISN'T
encrypted
and changing it to a .txt file somehow allows him to import the
data,
how is he to delimit it so that each column has the correct data?

or Start, Programs, Microsoft SQL Server, Import and Export Data,
go
through the wizard

So the wizard can magically make everything fit his needs?

it's not rocket science; and reinventing the wheel is never the
right
way to go.

It's not always rocket science, granted, but if you're REALLY
working
with anything more than a text file to begin with, your solutions
have
just damaged his data and given him nothing to show for his
efforts.
Is all you've ever worked with text files?



.

Loading