(no subject)

[fiercekitty.livejournal.com]

This is my last week at work (I'm a database administrator, working with an incredibly shittily-designed SQL database accessed through *shudder* MS Access) before I head back to university.

Almost all of my responsibilities have now been transferred to other people, so I generally finish my day's work by 10h00, barring anyone breaking any systems (happens less often than you'd think). Today I got it into my head that to use the remainder of the day, I'll redesign all of our internal Access forms to leave my legacy, so to speak.

Old design:


And the new design:


This is what I really want them to look like, though the pink stars are fun:

Comments

[jecook]

Uh, can't see the pictures.

[fiercekitty.livejournal.com]

oops. should be fixed now, thanks for the heads up.

[jecook]

In regards to the fist one:

ow.ow.ow.ow.ow.ow.ow.ow.ow.ow.ow.ow.ow.ow.ow.ow.ow.

I rather like the last one, usability wise. the socond one is cute, but too noisy. ;)

[jecook]

er, first one... ( although I imagine that people have wanted to put their fist in the face of the designer of that form...

[fiercekitty.livejournal.com]

the data entry department has taken to calling the first one 'the christmas tree form' XD

you don't like my stars? I was aiming for headache-inducing =/

[jecook]

Oh? it's right on, then. ::snicker::

[jahbulon.livejournal.com]

Holy Eclectic Screenshots Batman! That first form is frickin INSANE!!

I imagine new recruits see that form and shit themselves. Nice rework.

[fiercekitty.livejournal.com]

Well I haven't tackled the big one yet :X I'm scared of it. Oh well, I have all week!

I don't even know who designed that form originally. He sucks, whoever he was.

[ezerick.livejournal.com]

SQL based DB accessed with M$ Access? I'm so sorry... A badly designed DB makes me want to weep.... Examples?

[davidn]

Microsoft Access would have been a huge improvement on the SQL client that I had to use for my Databases course last year. It was a fairly anonymous Linux-based one that autosaved whenever it felt like it, had no explicit Save function, and crashed when you tried to drag and drop text or right-click. Using it was like some sort of psychological torture where you wouldn't ever be sure whether the work you'd done on it would be saved by the next crash or not.

What's actually so awful about using Access for an SQL database? I've never tried that, myself.

[infy.livejournal.com]

Ow. That form just turned my brain into a puddle of mush not unlike chocolate chip cookie dough ice cream left out in the mid-summer sun.

Holy clashing colors of death, batman.

[rrrebo.livejournal.com]

Would you like some data with your buttons? Sheesh.

[fiercekitty.livejournal.com]

Examples? Hmm. Well the best part is that the main table is in SQL...the other main tables are all in an access mdb on our server.

[fiercekitty.livejournal.com]

The only reason the main table got moved is because it got too big for Access, which can only handle 1gig (or two gig, I forget) files...so it's like we're just pretending that it's all still Access 9.9

[fiercekitty.livejournal.com]

My biggest gripe is that I can do most things in Access, but if I want to run a really big query, I get an ODBC timeout. No big deal right, I can just run the query in SQL...except if I have to run it by linking tables (only the big main table is in SQL), I now have to export all those tables to SQL, make sure they don't break, build a query, run the query, and export everything back to access. What a huge freaking pain.

[fiercekitty.livejournal.com]

That icon is disturbing XD

[infy.livejournal.com]

If I ever get off my lazy ass, I plan on adding... "Feeling like an RCI?" to it.

[lord-fidget.livejournal.com]

Agreed.. whoever made the half-@$$ed attempt at "designing" that first one should be taken out back and treated like a lame horse.