Re: NewEra - Migrating from 2.11 to 3

In article <04246D1A021BD111B9D400609709C874053AF4@NEWTRACEMAIL>, neill@traceplc.co.uk says... > Does anyone out there have any experience of this? I want to get a feel > for some of the pitfalls (outside of those stated in the manuals, eg the > new database access hierarchy) Our system contains its fair share of > complexity, and often we have NewEra code calling C functions. One of > the reasons we want to migrate is that NewEra 3 can communicate with > other 32-bit applications (specifically Visual C++). Does anyone know > how NewEra 2.11 could also communicate with such applications (we > believe it to be not possible). > > Neil. > > > Hmm... Any experience of this...??!?!?! At work we've had v3 since dec last year and we are still trying to convert our stuff properly ;-( (I must confess that the new hierarchy is bit of a pain to comply to if your sources don't in the first place.) Here are some points/pitfalls I've come across: 1. DON'T RUN THE SYS MIGRATION TOOL UNLESS YOU HAVE A BACKUP OF ALL YOUR SOURCES. The tool works on the original source as defined by your project database (ie your syspg4gl). I'm not sure if the tool modifies syspg4gl or not, but its probably good to back it up too. (The tool also doesn't work too well if your project is a partitioned server) 2. Read the docs for the app.builder... We had some many problems because we didn't receive any docs with the upgrade... so we were doing things incorrectly in most cases. 3. For dll's defining windows add the wif, and the 4gh (generated from WP) to the component. Otherwise use the 4gl and 4gh. 3. For dll's remember to export the 4gh's!!! (This is why you need to include the 4gh for wif files also). 4. Ensure that there is only one copy of a source file in your dir hierarchy.... if a 4gh exists in multiple places AB only sees the first one, and complains that it needs to be added to the component. (This one caused some many problems when one of the guys copied a file to several component dirs) 5. Sometimes when you check out a project and you try to compile it you may get what I call the stupid box, ie a message box with an OK button but no other message. The problem is one of the libs your project depends on is corrupted. Rebuild the lib and check it in. 6. You may get a problem compiling/generating makefiles because the 4gh/4gl's now contain a "PRAGMA" line defining where the source is located. Just remove the PRAGMA's or regenerate the 4gh/4gl from the AP, and regenerate the makefile. 7. I've found that if I create a project, add a component then try and check it in, it will often fail. To avoid this just checkin the empty project *before* you add the component. good luck.... denzil