Now that Rebecca is back......... I am trying to replace some MS Access tables with AS/400 PFs and I'm interested in hearing any gotchas, been theres, or sage advice of any sort. Every step of the way has held major surprises. I am using linked tables connected via ODBC. Every field has DDS where it is defined with ALWNULL and DFT(*NULL). Autonumber functionality is being replaced with PF triggers that retrieve values from a standardized next number server (J.D. Edwards.) Given that a whole lot of work needs to be done in a little bit of time I am experimenting with using MS queries to give the fields back their old - long - Access names to lessen the number of changes. In other words, I hope to only have to find where tables are currently referenced and change the name to the new query. That part seems to be working. But I still have some headaches: 1) Access always seems to think that the fields are 'full'. I have tried every which way to trim the trailing blanks from the alpha fields without success. If I have a 5 character field with 'CATbb' (b=blank) in it, then Access doesn't want to let me key anything in the fourth position until I get rid of the invisible blanks. If I go into DBU in hex mode and change positions 4-5 to hex'00' then Access displays the field normally AND lets me begin keying in position 4. I keep thinking that other people have to have found ways around this before. 2) Is there any kind of trick that allows resequencing a linked table via Access queries? Sure, it can be done in a passthrough query but I have to assume that they aren't updatable. Plus, I fear that Microsoft's SQL won't always be the same if you just remove the semi colon from the end of the statement. 3) Is a project like this simply a pain in the beginning or does it end up creating headaches that will long outlive the conversion process?
Login or Sign Up
- Log in with