Redesign

  • Thread starter Thread starter anthony
  • Start date Start date
A

anthony

I'm going to completely re-design my 15 year old database (while
retaining the data). Can anyone recommend any graphical tools that can
help me get my thoughts in order?
 
I am *so* pleased you said that because I've just ordered it! Pity
that the Step-by-Step book for 2010 isn't published until March next
year!!
 
SQL Server has a built in diagrammer that puts visio to shame.

It's silly to buy 3rd party tools.. everything you need is included
with SQL Server natively!
 
I'm going to completely re-design my 15 year old database (while
retaining the data). Can anyone recommend any graphical tools that can
help me get my thoughts in order?

Personally I wouldn't redesign the whole thing at one time. I'd work
on a bit here and there and get things working smoothly in production.
Rather than one big implementation effort.

Keeping the big picture in mind of course.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
 
Personally, I wouldn't take advice from someone that only works with
junior-sized databases.

Tony _TRIED_ to build ONE SQL Server database once.. and it was too
complex for him.
Does that mean it's too complex for everyone?

NO. It just means dumbfuck canadians should STFU and work on their own
db skills before trying to preach to others.
 
a a r o n . k e m p f @ g m a i l . c o m said:
Tony _TRIED_ to build ONE SQL Server
database once.. and it was too complex for him.
Does that mean it's too complex for everyone?

You haven't got a clue what Tony has or has not tried, nor the results he
attained.
NO. It just means dumbfuck canadians should
STFU and work on their own db skills before
trying to preach to others.

Naughty, naughty, aaron. Haven't you spent enough time on probation to
learn your lesson? I guess this shows you haven't. They may not allow
probation next time.
 
I'm going to completely re-design my 15 year old database (while
retaining the data). Can anyone recommend any graphical tools that can
help me get my thoughts in order?

Please ignore the response with the rude language and derogatory
comments.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
 
Personally I wouldn't redesign the whole thing at one time. I'd
work on a bit here and there and get things working smoothly in
production. Rather than one big implementation effort.

Keeping the big picture in mind of course.

I would say the key point is to do refactoring first. That is, go
through and rewrite the ugly stuff without changing any
functionality.

But one thing that can be done is to change the appearance. I've
been working on some tools to make it easy to choose a set of basic
form colors/fonts that are easily applied by calling a function in
the OnOpen event of your forms. Changing the appearance to something
more modern can help a lot with "buy-in" on the part of end users,
but if implemented as external code that sets up the form appearance
when it opens, it also future-proofs your app, since it makes it
really easy to change the parameters to suit future
needs/preferences.

While it is, of course, "only cosmetic," users' relationship to the
app is really affected by issues of appearance. If it looks old and
ugly, they'll think the app is old and ugly. It's really that
simple.
 
David-W-Fenton said:
While it is, of course, "only cosmetic," users'
relationship to the app is really affected by issues
of appearance. If it looks old and ugly, they'll
think the app is old and ugly. It's really that
simple.

Back in the day, 1959/1960, when I was a wet-behind-the-ears newly minted
programmer, long ago and far away, I worked on SAGE Air Defense software. A
more experienced field maintenance programmer (he had maybe a whole year's
experience to my 1/2 year) told me "one fix to the display is worth ten
fixes anywhere else in the system". He was probably correct in regard to
the impression on the Air Force personnel sitting at the display units.
And, I suspect that ratio has not changed greatly since that time.

But, silly me, I listen to my customers who want the database application to
solve their business problems rather than "waste" money making it look
glitzy and glittery. Thus, I like your approach, David. Have you considered
packaging the programs and selling them?

Larry
 
Back in the day, 1959/1960, when I was a wet-behind-the-ears newly
minted programmer, long ago and far away, I worked on SAGE Air
Defense software. A more experienced field maintenance programmer
(he had maybe a whole year's experience to my 1/2 year) told me
"one fix to the display is worth ten fixes anywhere else in the
system". He was probably correct in regard to the impression on
the Air Force personnel sitting at the display units. And, I
suspect that ratio has not changed greatly since that time.

I learned this lesson after bringing in first drafts and having the
client unimpressed because nothing at all looked different. Since
then, I've always made sure that the first time the client sees any
work product from me at all, it's clear from the appearance that
things are different.

For instance, in a recent app, I took this form:

http://dfenton.com/DFA/images/OriginalCustomer.jpg

....and converted it to this:

http://dfenton.com/DFA/images/FirstDraftCustomer.jpg

Note that one new feature is added (the search in the upper right),
but it has a completely different look and feel, while actually
adding nothing at all in functionality (though it does correct one
#Name error!).

That didn't end up being the final look the client settled on, but I
got buy-in from the beginning, even if the actual number of new
features was not that great, or that most of the new functionality
was behind the scenes and not terribly visible.
But, silly me, I listen to my customers who want the database
application to solve their business problems rather than "waste"
money making it look glitzy and glittery.

Well, it's not like my method doesn't require *some* changes,
particularly if you're using different font sizes than the original
controls (if they are 8pts you have to resize and reposition them if
you want to change to 10pts, for instance).
Thus, I like your approach, David. Have you considered
packaging the programs and selling them?

What programs? I have certainly considered working up the relevant
submodules into a sample database, but it's always a lot of work to
do that, and I still have a half dozen other such demo projects
half-completed!
 
sounds to me like you're not very good at finishing things.

and of course.. anyone using Jet for anything is just plain retarded.

Excel is more scalable than Access!!!!

-Aaron
 
eat shit Tony. Ever since you stalked me-- made webpages spreading
lies about me, wrote letters to my friends / coworkers-- I have the
RIGHT to say whatever the **** I want about you
 
Back
Top