hexagon logo

UPDATE command

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 used to loop and update stats automatically, never had problems. However on machines here that I update automatically not looping I have had numerous problems, mostly corrupt databases. I can't say they are related and don't believe it should be but that is the one common element. Another difference is before when I did not have issues it was small loops of 30-50 pieces and few dimensions (10-20). Now when I have problems it is a situation where I have thousands of transactions in a database with up to 50 dimensions or more. I'd be inclined to believe that would be more the culprit. Still though I can not say what it is that causes my recent woes. I used to have no issues with Datapage but now days it frustrates me to the point I gave up on it.

    I send all of my data comma delimited to a text file for importing when I need to into an application other than datapage (such as Excel). No issues.

    If you are not having problems with Datapage now, I am inclined to believe that automatically updating stats will not give you any problems. My hunch is that is not what is giving me my problems here.


    Good info, boogerboy, but I do have a question for you (weel, 2 anyway):
    1) Do you use seperate databases for each part or group of parts or are they all in one database? (I don't)
    2) Do you periodically clean out your database(s)?

    The reason for question #2 is because even when you delete things (parts, data, etc.) from the Datapage Database, it is NOT deleted, but just 'hidden' in the database where you can not see it anymore. Every 4 to 6 months, I cleanout the database, I archive off old jobs that have been sold off and are no longer here, delete the parts from the database, then do an ASCII dump of all the remaining data (all at once, works fine). I then make a copy of all the current database file (place them in a sub-dir), then copy an empty set of files to the databse directory, giving me a fresh start, I then ASCII load the still-current data and I am good to go. If you don't do this, sooner or later (sooner!) your database will grow to a size that will rival your virt-memory file size. Being construction, not production, parts/jobs typically are here for less than a year so I don't need to keep huge amounts of data in my databse.
Reply
  • I used to loop and update stats automatically, never had problems. However on machines here that I update automatically not looping I have had numerous problems, mostly corrupt databases. I can't say they are related and don't believe it should be but that is the one common element. Another difference is before when I did not have issues it was small loops of 30-50 pieces and few dimensions (10-20). Now when I have problems it is a situation where I have thousands of transactions in a database with up to 50 dimensions or more. I'd be inclined to believe that would be more the culprit. Still though I can not say what it is that causes my recent woes. I used to have no issues with Datapage but now days it frustrates me to the point I gave up on it.

    I send all of my data comma delimited to a text file for importing when I need to into an application other than datapage (such as Excel). No issues.

    If you are not having problems with Datapage now, I am inclined to believe that automatically updating stats will not give you any problems. My hunch is that is not what is giving me my problems here.


    Good info, boogerboy, but I do have a question for you (weel, 2 anyway):
    1) Do you use seperate databases for each part or group of parts or are they all in one database? (I don't)
    2) Do you periodically clean out your database(s)?

    The reason for question #2 is because even when you delete things (parts, data, etc.) from the Datapage Database, it is NOT deleted, but just 'hidden' in the database where you can not see it anymore. Every 4 to 6 months, I cleanout the database, I archive off old jobs that have been sold off and are no longer here, delete the parts from the database, then do an ASCII dump of all the remaining data (all at once, works fine). I then make a copy of all the current database file (place them in a sub-dir), then copy an empty set of files to the databse directory, giving me a fresh start, I then ASCII load the still-current data and I am good to go. If you don't do this, sooner or later (sooner!) your database will grow to a size that will rival your virt-memory file size. Being construction, not production, parts/jobs typically are here for less than a year so I don't need to keep huge amounts of data in my databse.
Children
No Data