This File is becoming a real problem for me.

Filemaker seems to be crashing with this error (fmeng10.dll) it happens when i go into one of my layouts that is pulling in a lot of data from my child database file. All fields that it is pulling in a indexed and is holding 102356 records.

Master file is still very small at this stage.

The problem is once this error accours, opening the file sometime damages the child database which means i then will need to do a recovery on the file.

Could anyone help me on this issue. My solutions goes live on 02/04/02..........

Many Thanks,

Martin Williams

If it's a .dll file that's causing the crash (meaning you're in Windows), chances are the .dll file itself is corrupted. Try uninstalling and then reinstalling Filemaker (I believe Windows has an "uninstall" feature somewhere in the Start menu).

Hello Again,

I have tried un-installing and re-installing filemaker but still getting the same problem.

Could it have something to do with the amount of data that i am bring in on that layout. Their is a portal that some of the data is being brought in on. :?

Regards, Martin

Instead of doing a recover. Try saving your child file, as a compressed copy, then a second time as an empty clone. Then import the data from the other file into it.

It there is corruption in your child file, this may take care of it.

Also - when you uninstall and reinstall FMP, make sure you get the whole thing! Sometimes, if you have several version of FMP (eg FMP 4 and 5) it will leave the shared dll files that may be the problem. So unistall ALL versions of FMP.

I don’t know if this has anything to do with your problem, but take a look at the article 104595 on the FMP homepage. Sounds at least similar!

Otherwise, this could just be one of those Windows things. It may well be that the problem shows itself in FMP, but is actually generated by another program. This is usually the case with DLL errors. Try a fresh Windows installation.

Sorry I can’t help more

Rigsby

Hello Again,

Many Thanks to everyone on this issue,

To solve this problem i re-built the child table and at this stage everything is working fine. A 56 meg file was re-built down to 21 meg. ( Think i did a good job )

Once again many thanks,

Martin Williams

quote:

---

Originally posted by partsgb.martinw:

A 56 meg file was re-built down to 21 meg.

---

This seems like as good a time as any to mention the value of "Save a Copy As..." and then saving a compressed copy. In this case, the value is about 35MB!

Agreed, However if this is a file that is updated every week from a SQL server, it's a lot of work to keep "saving As".

The rebuilt of the child table was also taking out fields that i really didn't need which is encluded in my filemaker templete that i have created.

However another note is that an un-control shut ( PC Crashes) down can cause file damage and although filemaker has the recovery mode.In my case i felt the recovery did't fix everything and the best thing to do was start again.

Take Note >>> MAKE BACKUPS

Regards, Martin