Philip Colmer

I'm starting to get errors from the software when I search for individuals. The messages I'm getting are: Record is out of range. 48 REPPUSH Nesting error. 57 REPPUSH Index does not match the table. Delete the index file and re-create the index. 81 REPPUSH I've tried Maintenance > Reindex and Maintenance > Validate File Integrity. I didn't get any errors from the former option, but the latter initially fixed 501 potential problems and also reported that "Memo file FAMILY_PD.FPT is missing or is invalid. 10638 FIXLOSTRELATIONUID". As far as I can tell, the file is indeed missing but I don't know how to recover from this. Any suggestions on what I can do? Thanks. --Philip

Yes, I've tried the settings you specified and I'm still getting the problem. Yes, it is the decendant indented chart. Thanks. --Philip

I was speaking generally from the perspective of how Windows communicates with applications. For example, if you try to interact with an application's window, Vista sends messages to the application to inform it of that interaction. If the application doesn't react to the messages, Vista marks the application as not responding. If the application subsequently "springs to life" and collects the pending messags, the "not responding" flag is cleared. In the case of TMG, I think it is simply that TMG is hard at work and not multitasking in a smooth manner. --Philip

I'm finding that the output from the Descendant Box Chart can sometimes result in people being placed quite a distance away from where the software *ought* to be able to put them. One extreme example I can give is where I've got the report configured for left to right layout and it puts the primary focus person on page #1, and then *everyone* else on the second page. The thing here is that I can easily select everyone and put them back onto page 1, so I'm not sure why the software thinks it needs to start a second page. A less extreme example is a top to bottom chart with UK lines. Here, the software seems to be putting a big horizontal gap between spouses. Again, the boxes could be fitted in closer and the net result is that more sheets of paper are used than could be required. --Philip

Virginia Thank you for this suggestion. Unfortunately, I think you've misunderstood me. It isn't that the chart is failing to include everyone - the problem is that it is including "unknown spouse" where no such person exists in my data. I don't know why it thinks that these additional spouses exist. I don't know if it is a bug in the report or a problem with my database. --Philip

Thanks, Virginia. Check the web site was already set to 0 and check for messages was set to 7 days. I've also seen this when TMG is creating reports. For example, creating a descendant indented chart with 87 people can take long enough that Vista changes TMG's title bar to show "Not responding". As I put in my earlier reply, this happens when Vista has tried to send an application message to TMG and TMG hasn't reacted in a timely manner. That may be a different "slow performance" issue compared to what other people are reporting, I admit.

I've created a chart and there are a couple of places where the report states "+unknown spouse" where it shouldn't be. There isn't such a person in the data. TMG 7.03 UK edition, Vista 32-bit. --Philip

I'm also seeing slow performance in TMG, particularly when starting up. It can get so bad that Vista starts to report the application as not responding. It comes back to life if you leave it long enough, but it looks like something is taking its time within TMG and not "listening" to the messages from Windows.