Hi Mapics ML: I want to thank you all for your assistance in this matter. I ended up using DFU to edit the file after I located the appropriate Relative Record Numbers of the records I was correcting by putting the DB file in Query/400 with no sorting. Using this information, as Peter Vidal pointed out, I could have used this information and done the editing with DBU. I do have some specific comments to my assistors: To Jim Wiedl: Our company's version of DBU must be very old because it doesn't behave as you suggested in your posting. How do I find out the verion of DBU that is in our system? Isn't there a Control Language command that will bring up this information? To Peter Vidal: Thanks for expanding on the DDS specs as mentioned by Jim Wieldl. I will pass this information to our Information Systems person and get some implimentation guidance from him. To Paola Groeber: I tried using your suggestion and I'm afraid that the Cmd 6-SCN function is really over my head. I'll have to study the help screen more and see if I can get a better understanding of its function. Thanks for the suggestion. Again to everyone, thanks for your timely comments and suggestions. Regards, Al Gershen Grants Pass, OR email@example.com ---------- Original Reply Messages ---------- >From: "Jim Wiedl" <WIEDLJ@timesaversinc.com> >Reply-To: firstname.lastname@example.org >Date: Mon, 11 Feb 2002 13:25:30 -0600 >When viewing a file with DBU you can use cmd4 to see the keys to that file. >From the same first screen cmd10 will give you a pop up menu and you can >expand the first option FILE. Take a 7 for data base relations. This will >show you all the logicals over your file. If your file is in record number >order from the same pop up menu from cmd10 you can do a search for a value in >a particular field. If you created the file via query it most likely will not >be indexed. You may need to create dds specs with a defined key and copy your >query data into it. > From: Peter_Vidal@pall.com Reply-To: email@example.com Date: Mon, 11 Feb 2002 14:32:36 -0500 > >"What is the difference between a "keyed" and "non-keyed" DB file?" >If you are going to use this file regularly, you should create a DDS for the >file and select a field to be your key(s), for example: > >A UNIQUE >A R BOOKR >A BIRPGR 3A TEXT('REPORTING GROUP') >A BISHIP 13S 2 TEXT('SHIPPING AMOUNT') >A K BIRPGR > >Use UNIQUE to have non-repeated keys in your file; if you do not use UNIQUE, >you >will still have a keyed file but you could have repeated keys in it. A >non-keyed file is simply a sequential file that you will have to roll down-up >if >you use DBU for example. > >However, whenever you use Query/400 to create a file, it will be a "non-keyed" >file. > >"Is there any way to convert a "non-keyed" DB file into a "keyed" DB file? " >I do not know about a command that can do that but you can take the first >approach that I mentioned or create a keyed file and copy over the data you >have >created with Query/400. This could be tricky so try to define your layout >based >on the results of your query file or at least with the same field names. You >can use CPYF command with the *MAP option. > >"If there isn't a way to do this, I do I use DBU to go directly to a specific >record on a very large DB file?" >You can still use DBU to access your file by relative record number. > >Peter Vidal >Programmer Analyst >PALL Aeropower Corp. > From: Paola Groeber <firstname.lastname@example.org> Reply-To: email@example.com Date: Mon, 11 Feb 2002 14:47:22 -0500 >If the inhouse DB file is not keyed, you can check to see if there is a >logical built over it by using F14. This should bring up a list of the >logicals on the file or the file itself. It lists the key fields used. Once >you have selected a keyed file, you can use the F6 key to position to a >specific record using the key fields that function key provides. > >Good luck. > >Paola Groeber >Former MAPICS Business Analyst for CRM applications >Also DBU Guru for over 12 years :^) >firstname.lastname@example.org > ------End of Original Reply Messages------
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.