When I go into the my database it shows only 1 record but if I do a search it shows the complete found set although on the status area records: 1

If I then select 'Show All Records' it reverts back to 1 record in total

Any ideas?

Thanks

Nick

Nick, if you search for * in a field where all records have an entry, what is returned for "Records:" and what is returned for "Found:" in the status area?

Jerry

Hi Jerry,

Ok, Records: 1, Found: 151348 - I can also scroll up and down the records using the scroll bar!?

Cheers

Nick

1 record but 151348 found? Wow, that's bizarre. My first step would be to immediately uninstall FM and then re-install it, but i have to admit i've never heard of anything like this. Hopefully someone else knows more than i do --that usually seems to be true : )

J

Nick:

How many records *should* there be in that file?

-Stanley

Hi, Nick! I'd suggest exporting all record data immediately before you lose all your data. It only takes a minute and can save you a great deal of grief if you're db goes bad, which to me it sounds like it is. Then, working from a copy, delete all records and re-import the data and see how it behaves... and do not throw away that original export... keep it w/your backups just in case.

There's nothing else going on w/the db, right? I mean, it's not web-shared, it's not using any passwords or restrictions, you're accessing it directly and not from a server, etc.?

--ST

I agree with Steve about exporting, but I'd still like to know how many records are expected to be there. One seems to be too few, and it sounds like maybe 151348 is not the expected number either? I'm really curious to know what's going on there.

-Stanley

151348 is the right amount of records so no problems there

Normally we access the database from a server but I get the same problem if I access it directly

I'll make the back-up now!!!

Cheers

Nick

You mean the file is on a network volume (file server)?

Yes it is but even if I shut down fm server and open the file just using fm5 pro I still get the same problem

Nick

Hi, Nick! I think Vaughan was double-checking that you were using FileMaker Pro Server sofware and not just having users log on to the file server and double-clicking the database from a mounted volume (which he would probably warn that doing so can cause db corruption). He also recommends keeping an empty shell of your databases in case the "live" one goes bad... that way, you can just export your data from the bad one and import the data back into a copy of the shell.

--ST

I ran into this same problem. Never figured out what caused it but was able to fix it by running a recovery on the file.