Re: Existing Database - Create new or Fix existing?

Mike, please use that information intelligently. The fact that the utility
identifies an issue does not mean it is an application killer.

The issue of reserved words as field/table names is a thorny one. You might
get away with it, or you might hit scenarios where the names are
misinterpreted. If you have spent lots of time developing the app, and it
seems to be working fine, you might continue to use the app and just keep in
mind that this could be an issue of a problem crops up.

Most of the other issues can be addressed without the need to redesign the
whole app. For example, if you use spaces in your field names, adding the
square brackets around the names will slow you down during development, but
will not cause your appliction any problems once you have it developed.

Similarly, if you have relationships without refential integrity, you can
fix any bad data that may have crept in, set up the relationships correctly,
and continue using your application.

My suggestion would be that if you are experiencing problems and
inconsistencies and the issues are significant enough for a complete
rebuild, feel free. Otherwise, fix the issues you can (such as ensuring all
tables have a primary key, and foreign keys are not unintentionally
orphaned), and keep the others in mind as you maintain your application.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"BetaMike" <BetaMike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CE7C649B-8601-449D-9F3A-A8DE1446B1DA@xxxxxxxxxxxxxxxx
Hi,
I downloaded the free 'database checker' utility from
http://www.allenbrowne.com/AppIssueChecker.html and used it to analyse our
company database. The results are NOT good (54 page report!)

So...
Do I trawl through the report page by page and try to fix the issues one
by
one or should I create a new one from scratch?

I'm thinking of copying the database and then dropping each table into a
new
database, fix all the bad naming conventions etc. and then design new
queries, forms and reports later. Any advice would be most welcome.

Thanks.


.

Relevant Pages

  • Re: Third party tool required
    ... How does this fix data corruption? ... wrote our own table header repair utility because they would ... > What's so hard about writing your own database rebuild utility. ... > In our app we call this utilty installDB. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Existing Database - Create new or Fix existing?
    ... I built the app in 1997 and have been adding to it ever since. ... Dozens of queries, forms and reports ... I'll continue to use the 'database checker' as I build and will no doubt be ... Can I fix it or should I leave it ...
    (microsoft.public.access.queries)
  • Re: Error Accessing File - Network Connection May Have Been Lost
    ... "Immanuel Sibero" wrote: ... >> I'm getting this message whenever I try to compile my database. ... >> it when I try to access the code for a report. ... >> Compact and Repair does not fix it. ...
    (microsoft.public.access.reports)
  • Re: Existing Database - Create new or Fix existing?
    ... that's one way to learn about how to build a database. ... data - forms, subforms, combos, list boxes, reports, and so on. ... I built the app in 1997 and have been adding to it ever since. ... Can I fix it or should I leave it ...
    (microsoft.public.access.queries)
  • Re: Error Accessing File - Network Connection May Have Been Lost
    ... HTH, ... > I'm getting this message whenever I try to compile my database. ... > it when I try to access the code for a report. ... > Compact and Repair does not fix it. ...
    (microsoft.public.access.reports)