I use datapage V3.33 on a few CMM programs, 3 days ago it was working fine on a particular program and datapage was recording correctly (400 recordings). When running the program I have trace-fields to track work order # and serial number (also saved in datapage). Now when the program runs, datapage records over the previous trace fields (w/o, serial # and stat count #) along with overiding the measured value. I have tried a few things without success, anybody have an idea what can be done or what happend?
I think you are running a query, or selecting options to filter and show only certain data without knowing it. I've never heard of this issue before. The evidence of why I do think it is submitting is the updating of the tracefields. Are you sure you are looking at a unique new transaction, or are you looking the "last" transaction only? A screenshot might help.
It allows me to pull up many other transactions previously to the date this caused an issue. The error that shows up is "database user error -19 record not legal member" which to me sounds like I dont have rights to pull up or save the information. My SMA agreement has run out, but I should still be able to use datapage and save to datapage.
-19 sounds like trouble. Ascii dump as much data as you can & create a new database, ascii load the data.
You say you have a few CMMS. How are you putting data into the database? Is there just 1 database across a network? Are all CMMs using the same database? Unless all paths to the database are exactly the same, there could be corruption issues. If one updates using "S:\database\path" and they are all using the same database, all updates must use "S:\database\path". This includes someone on the local computer looking at the database.
-19 sounds like trouble. Ascii dump as much data as you can & create a new database, ascii load the data. You say you have a few CMMS. How are you putting data into the database? Is there just 1 database across a network? Are all CMMs using the same database? Unless all paths to the database are exactly the same, there could be corruption issues. If one updates using "S:\database\path" and they are all using the same database, all updates must use "S:\database\path". This includes someone on the local computer looking at the database.
Yes I have 2 CMM's using datapage and they were both dumping information into the same database across the same network (worked fine for 2 weeks this way). In fact I think what happend is both CMM's were running the same (no not exactly the same, some edits are different) program and dumping into the same file name for datapage. I think what happend is they both finished checking the part and started dumping information into the same file at the same time. One CMM I started a new location on the same network for its database and it is working fine now, the other CMM is still having issues with this error. I have cleared the Xstates file and tried creating another database but I come up with the same error.
Thanks for everyones help, if I cant get it today I plan to call tech support and donate $250.00 to Hexagon.
I was able to get it working again after setting up a new database location on the same server (tried it yesturday but I must have forgot to delete the xtat file), so that part is working now (I did need to delete the xstat file since it had been log jammed and is working). So without having to go through all my programs and re-assign the location to save to the new location is there something that can be done with the current database so it will work correctly?
I need to do this by opening each program and F9 the datapage portion and re-assign to the new database? I was hoping for a quick short-cut without having to do that with the 50+ programs.....Looks like my day is screwed!!
