hexagon logo
Register Sign in
  • Replies 4 replies
  • Subscribers 9 subscribers
  • Views 91 views
  • Users 0 members are here
Options
Related

UPDATE command

Matthew D. Hoedeman
I have known about the update command and have even posted it as a possible solution for other users. I have never used it.

So, my question is, have any of you ever had any issues with using the UPDATE command?

I know some of you have had issues with databases getting messed up and then never being able to get any of the data back out of them, do you same people use UPDATE?

The reason I am asking is that I am going to ahve to run a rather large study soon (like, 300 or more!) and I want to automate the process as much as I can. Looping, UPDATE, that kind of thing, with a simple COMMENT to pause the loop and just pressing the DONE button on the remote to get it going through the next cycle. But, for obvious reasons, I do not want to risk losing any of the data and then have to start over (THAT WOULD SUCK!!!!!!).

So, are there ANY draw-backs to using the UPDATE command? What is gonna bite me in the rump on this?
Parents
  • I have separate databases for families of parts or customers. Each database typically contains several part numbers (CMM programs). In regards to number 2 what I do is when the database starts getting big I move it to a backup location and create a new database. I only ASCII dump info when I have to send it to someone for analysis that does not have Datapage.

    I think you'll be fine. I am inclined to believe (can't prove it) that my issues are related to size/amount of transactions or data. When I started archiving large databases and starting fresh I ran into less issues. But then it became more work and a pain in the butt to merge data.

    These days I am fine with text files. They are shareable which is nice as I am finding less and less people that have or even want Datapage. The ASCII dump for Datapage is nice for that too though.
Reply
  • I have separate databases for families of parts or customers. Each database typically contains several part numbers (CMM programs). In regards to number 2 what I do is when the database starts getting big I move it to a backup location and create a new database. I only ASCII dump info when I have to send it to someone for analysis that does not have Datapage.

    I think you'll be fine. I am inclined to believe (can't prove it) that my issues are related to size/amount of transactions or data. When I started archiving large databases and starting fresh I ran into less issues. But then it became more work and a pain in the butt to merge data.

    These days I am fine with text files. They are shareable which is nice as I am finding less and less people that have or even want Datapage. The ASCII dump for Datapage is nice for that too though.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement