Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Database Design / April 2005

Tip: Looking for answers? Try searching our database.

too many fields defined access table

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Sandy K - 25 Apr 2005 03:24 GMT
Hi:
I have "inherited" a database that has the main table maxed at 256 field
defined.
Any suggestions on how to clean this mess up easily?

Thanks

Sandy K
Duane Hookom - 25 Apr 2005 03:27 GMT
Start analyzing and normalizing.

Signature

Duane Hookom
MS Access MVP

> Hi:
> I have "inherited" a database that has the main table maxed at 256 field
[quoted text clipped - 4 lines]
>
> Sandy K
Sandy K - 25 Apr 2005 03:43 GMT
I tried to do that, but apparently multiple unqualified people have worked on
this database over the past two years and linked tables to non-existing
sources. Every time I try to isolate the problems, it becomes a tangled up
mess. They never even created sufficient relationships or switchboards. It's
quite a challenge. Unfortunately the whole company is currently using this
mess as a tracking system. Over 30 forms involved and a lot of computer
illiterate people that will go into cardiac arrest if I change too much at
one time. Sorry if I sound like I'm whining. When this was created, no one
even new how to create a report or report. Every time they needed to extract
information that made a completely new query instead of modifying what they
had. There are over 300 queries and probably that many macros--someone didn't
underestand the difference between the two. (I honestly have never seen such
a mess before). If there weren't so many forms involved, I would have just
started a completely new database, but VP doesn't want me to make too many
changes--due to widespread computer panic. It if wasn't my task to fix it, it
would be pretty funny.

Thanks again.

Sandy K

> Start analyzing and normalizing.
>
[quoted text clipped - 6 lines]
> >
> > Sandy K
Duane Hookom - 25 Apr 2005 04:37 GMT
Is there a question in there?  I would probably start by documenting with a
3rd party product like those available from FMS
http://www.fmsinc.com/Products/access.asp.

Signature

Duane Hookom
MS Access MVP

>I tried to do that, but apparently multiple unqualified people have worked
>on
[quoted text clipped - 35 lines]
>> >
>> > Sandy K
Sandy K - 25 Apr 2005 05:46 GMT
I think that I have gotten my answer. I probably will have to start all over
and create a new database. There seems to be no quick solution to multiple
creator errors-- especially since there isn't anyone in my company that can
tell me who, what, when or why the tables are set up the way that they are. I
did try to analyze and normalize, but the wizards couldn't help me. I will
take your suggestion and look into FMS.

I appreciate your input.

Have a great week!
Sandy K

> Is there a question in there?  I would probably start by documenting with a
> 3rd party product like those available from FMS
[quoted text clipped - 39 lines]
> >> >
> >> > Sandy K
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.