mogabog Posted February 3, 2005 Share Posted February 3, 2005 I have a database, and I am going to duplicate it, strip the data and build up a new database (they will work in very simialr ways). However I notice that the RecID's for my CDML web files are still vey high numbers, and I'd like to bring them back down - so how do I "reset" the database to think it is young instead of old? Thanks A Link to comment Share on other sites More sharing options...
rdhaden Posted February 3, 2005 Share Posted February 3, 2005 Why do you care what the RecID is? I would instead use my own record serial number, an auto-enter non-modifiable number field, starting with 1 and incrementing by 1. Link to comment Share on other sites More sharing options...
mogabog Posted February 3, 2005 Author Share Posted February 3, 2005 Sure, I do that already, but this is a CDML published datbase, so when someone need to edit a record, it is given a RecID by FM, and these RecIDs are not modifiable, and are high numbers. It does not particularly matter, but if it is possible to reset the databases to low number RecIDs, then I would like to do that. Link to comment Share on other sites More sharing options...
Mike D. Posted February 3, 2005 Share Posted February 3, 2005 Why not just create a clone of the database? That would do exactly what you want. Link to comment Share on other sites More sharing options...
mogabog Posted February 4, 2005 Author Share Posted February 4, 2005 b/c then I have to start from an empty database, redo all the relationships, fields, calculations, etc. and I would rather not. A Link to comment Share on other sites More sharing options...
Mike D. Posted February 4, 2005 Share Posted February 4, 2005 I didn't notice that you were using FM6. The clone method works great in FM7. When I update a database that is at a customer site, I just bring in a clone of the update and run an import script. Works great every time. Mike Link to comment Share on other sites More sharing options...
-Queue- Posted February 4, 2005 Share Posted February 4, 2005 Creating a clone will work fine. The only thing it will lack is records--all relationships, field definitions, and scripts will be left intact. Then just change your RecID's field definition to start with a lower number. Link to comment Share on other sites More sharing options...
stanley Posted February 4, 2005 Share Posted February 4, 2005 When creating a clone, you'll also lose any globals you had pre-set. It might not matter, but it can catch you out if you're relying on it. -Stanley Link to comment Share on other sites More sharing options...
-Queue- Posted February 4, 2005 Share Posted February 4, 2005 Very true, in which case importing a single record from the original db, with auto-enter options not performed, and including globals in the import order, then deleting the record, will resolve that issue. If you only have a few globals about which you are concerned (I would think containers are the primary issue), copy/paste is also an easy option. Link to comment Share on other sites More sharing options...
stanley Posted February 4, 2005 Share Posted February 4, 2005 Yes. When I create clones for the customer to use in case they do an emergency Recover, I always import a single (seemingly blank) first record into it, to preserve globals, (yes, I forgot) containers, etc.) -Stanley Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 7021 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