FMPRO-L Archives

September 2010, Week 4

FMPRO-L@LISTSERV.DARTMOUTH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Tim Mansour <[log in to unmask]>
Reply To:
FileMaker Pro Discussions <[log in to unmask]>
Date:
Wed, 29 Sep 2010 05:58:36 +1000
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
Don, have you tried rebuilding indexes first? Turn off indexing for each field and let FileMaker rebuild as necessary. 

Tim Mansour <[log in to unmask]>
Neologica Print & Promotions ABN 63 904 335 408
Certified FileMaker 10 Developer
PO Box K1163 : Haymarket NSW 1240
Mobile 0405 500 846

On 29/09/2010, at 5:18, Don Wieland <[log in to unmask]> wrote:

> Sigh...
> 
> I have a client's solution in where in two table there is a one record that I believe is corrupted:
> 
> - I have a specific relationship where the record relates to it even when the key fields to the records DO NOT match.
> 
> - When I delete it, it disappears, but when I do a search on it again, it shows up with "?"'s in all the fields and the found set says 0/1 records displayed.
> 
> I have my own plan of trying to get rid of these records, BUT was hoping that some one might share with me some quicker (or at least more efficient) way to handle these corrupted DBs.
> 
> I'd appreciate any thoughts or recommendations on this. I have to deal with this issue this week and could use some insights. Thanks ;-)
> 
> Don Wieland
> D W   D a t a   C o n c e p t s
> ~~~~~~~~~~~~~~~~~~~~~~~~~
> [log in to unmask]
> Direct Line - (949) 336-4828
> 
> Integrated data solutions to fit your business needs.

ATOM RSS1 RSS2