Upgrade from Access to ADP/SQL-server

  • Thread starter Thread starter reidarT
  • Start date Start date
R

reidarT

I am planning on changing platform from mdb to SQL. The main table in the
applicastion has 61 fields, and I wonder if this is too much. Should I split
it in several tables and use a view or stored procedure on the form where
data are added and updated?
regards
reidarT
 
Whether it is correct or not to have 61 fields in the table depends entirely
on whether those 61 fields accurately represent attributes of a single
entity.

A good relational design is a good relational design, regardless of whether
it is implemented in Jet or SQL Server. If it was correct to have 61 fields
in the table in an MDB, then it will not become incorrect because you are
now using SQL Server. Equally, of course, if it was incorrect in the MDB, it
will remain incorrect in SQL Server.

Without knowing what attributes of what entity are being modelled, I can not
be any more specific than that.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.
 
I've had 250 fields in an ADP and it works like a charm

really depends on what the fields look like
 
Back
Top