NewEra 2.x --> 3.x upgrade success stories?

I'm interested in hearing from anyone who has taken a legacy NewEra application from 2.x to 3.x (specifically, NE 2.11 on Windows 3.x to NE 3.11 to NT 4.0). If AFCL is involved, and/or have at least some of your SQL imbedded in the SuperTable events, so much the better. I'm finding numerous "performance differences" that is making this upgrade quite a bit longer than expected. I think most of the differences I'm finding are in NewEra, not the OS.

Dennis Pimple wrote: > > I'm interested in hearing from anyone who has taken a legacy NewEra > application from 2.x to 3.x (specifically, NE 2.11 on Windows 3.x to NE > 3.11 to NT 4.0). If AFCL is involved, and/or have at least some of your SQL > imbedded in the SuperTable events, so much the better. > > I'm finding numerous "performance differences" that is making this upgrade > quite a bit longer than expected. I think most of the differences I'm > finding are in NewEra, not the OS.Dennis, We have successfully moved our NewEra 2.2 application to NewEra 3.11 As you are finding, it took considerably longer than expected. We don't use AFCL, but have considerable SQL embedded within the events. Although the performance of the end product on Win95 is disappointing for us, NT seems to be quite acceptable. A couple of the problems I remember off hand: - In most cases, we had added to the 'finish' event to handle if the window was being closed by the system action (clicking on the'x' of the window). There appears to be a change so that the 'close' shouldn't be called in these cases whereas in 2.2x it had to be - All the object resources for a window are not automatically when the window is closed and a new function must be added (see release notes for notifyClose()). The notes were not very clear to us and it took quite some time to clear up what had to be done. All objects used in the window outside the SuperTable, including the supertable itself but not including the menu bar, had to be specifically set to NULL. Let me know if there's anything else we can do to help. Pat Navas

Dennis it appears that 'the powers that be' killed my last post on this subject; I will try to be less critical this time. We also are in the process of migrating from NE 2.1 on Windows 3.1 to NE 3.11 on NT4, SP3 using AFCL. We have found that the process is very slow. The most noticeable problem we are finding is an error msg. that appears every time we do a build. Tech. support is looking into it and as of yet they haven't found a solution. There was a question as to whether we would be able to get the deployment licenses for NE 3.11 but our inside salesrep has assured us that they should be available. Overall the entire dev. environment runs extremely SLOW. We are hoping that this is just a setting issue. Although I don't see many posts to this NG for NE problems I will post any solutions Informix comes up with. Hopefully they will help someone. Brian Dennis Pimple <dennisp@informix.com> wrote in article <7981ki$pdn1@webint.na.informix.com>... > > I'm interested in hearing from anyone who has taken a legacy NewEra > application from 2.x to 3.x (specifically, NE 2.11 on Windows 3.x to NE > 3.11 to NT 4.0). If AFCL is involved, and/or have at least some of your SQL > imbedded in the SuperTable events, so much the better. > > I'm finding numerous "performance differences" that is making this upgrade > quite a bit longer than expected. I think most of the differences I'm > finding are in NewEra, not the OS. >