Sixdots Posted October 22, 2008 Posted October 22, 2008 I am having problems with my database served on fm server 8 I have a main file with 1,600,000 records. It keeps losing records. I`m not sure if the problem is with fm server so I am trying to find out what version of fm8 server I have. I would like to install the latest version
IdealData Posted October 22, 2008 Posted October 22, 2008 The "FileMaker Server Admin" utility will reveal all. The latest v8 server is 8.04
Steven H. Blackwell Posted October 22, 2008 Posted October 22, 2008 By all means be sure that you are reunning the v4 edition of FIleMaker Server 8. However, when you say "loosing records" this may indicate far more significant issues that the v-rev. What appears to be happening exactly? Do you enter records and then are unable to find them? Does the record count increment when you add records? Steven
Sixdots Posted October 22, 2008 Author Posted October 22, 2008 I must be blind I looked at it this morning and it was right there 8.0v4 Thank You
Sixdots Posted October 22, 2008 Author Posted October 22, 2008 I`m not sure what is happening We have 6 users 4 running FM8.5, 1 Fm 8.5 advanced 1 FM 9 all accessing the database from Fm server 8.0 v4 which is on a separate server in a remote location using the internet to access The database we are losing records from has about 1,600,000 record in it. It has about 20 records added per month and is used for mainly reference It shows part locations prices etc When we lose the records it they are mostly the ones we have locations for our inventory Out of the 1,600,000 records we have about 2500 records with locations. It has happened twice in the last week where we lost about 1600 records one time and about 800 records the last time I know this does not give you much to go on, I am trying to replicate the problem and will keep you informed Yes when records are added the count goes up
Vaughan Posted October 23, 2008 Posted October 23, 2008 There could be a lot of causes. It might be as simple as users deleting records. It might be a process that deletes records. Look in the relationships for any that have "delete" option enabled. This isn't a bad thing in and of itself (I use it all the time) but it can be when a self-join (or something) causes cascading deletes to occur. When this happens, the deletion of one record causes many more to be deleted.
Recommended Posts
This topic is 5876 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now