[AccessD] On DB Bloat, Bad DB Design, and various

<snip>  
>
WOW way to burn time... you obviously didn't have the right tools for 
the job, because if you can ADD and you can DELETE a field, then you can 
ALTER... and it takes no more than a few minutes, that's w/ the time it 
takes to find the field and either write up the command or use a gui 
interface to do it all... 2 fields, that's nothing, you were just using 
a hammer....

<snip>

Actually, the 'web interface' tool, that their IT department let me have
access to had Add and Delete LINKS.  I then had a place to run querries.  I
couldn't tell if I could run 'scripts' or not.  I used my 'copy' on my SQL
server, to make a script to do the job.  However, what I have at home is
named differently, and I was 99% sure I didn't have all of the latest design
changes, so I had two problems with trying to use a script to solve.  One, I
couldn't use the script MY Enterprise Manager created, without modifying it.
And to modify it, I would have had to dig through all of the changes that
were made to the current system.  Two, I wasn't even sure if it would run a
script.  I said Query, not script.  So I used the links provided, and query
capabilities provided.

I may not have had done the process perfectly.  I'll definitely admit that.
Of course, the correct way this should have been solved, is for their IT guy
to go to the console with Enterprise Manager, and change the field
properties and click okay. Work done.  However, it was a live system.  I was
getting zero support from their IT department, so I used a method I was
confident I wouldn't screw up their LIVE data with.

<snip>

>Now think about that, is setting a field size limit to something close to
>where you think your client won't exceed worth $150 a pop?
>  
>
No it's not, and you ripped off your client.  Sorry, but unless that's what
you charged for just showing up, that's a rip.
-- 
-Francisco

No, I didn't rip off my client.  It took me an hour and a half to fix a
problem HE created.  He knows it, I know it.  Am I supposed to spend my time
fixing his mistakes for free?  There was somewhat of a time pressure
involved, and I was handed a tool to 'work with' SQL Server that I had never
had before.  I didn't have any other access to their system.  (I couldn't
even create an ASP page to do what I wanted to do.) I only had access to
this 'web tool'.  So trust me, he got off light, with it only taking 1.5
hours.  He had already spent FIVE hours trying to figure out how to do
anything in that 'web tool'.

Drew