Re: Will New Era 2.12 exe's run on win95????

John Clynes wrote: > > Can New Era 2.12 for win3.11 EXE's be deployed under win95/98??? > Are there any issues? Yup. In 2.12 some of the runtime DLLs were not correctly working and therefore not reantrant. Running more than one NE application under 95 or NT caused probs... this is the main reason for upgrading to 2.2 if you ask me. 2.2 works fine under borth 95 and NT. > > Also, I've heard that NE2.12 isn't necessarily y2k compliant (code). Any > ideas for (fast) working out if all my existing NE2.12 projects have been > coded to be y2k OK or not (barr setting clock forward??) Yup. Trivial errors can be found like that. Only make sure not to set the date too far in the next century (or do exactly that -- you will just _love_ how NE handles 1.1.2040 :>). > > Also, if anyone has converted NE2+ to NE3.10+, can you advise me of the > ease/difficulty in doing this. Should be exactly the same as upgrading from 2.2 ... the only little difference I remember was that 2.2 doesnt set a busy cursor to normal automatically anymore after a new (main?) window is opened. Differences between 2.x and 3.x are documented in the documentation. But _never_ use the automatic upgrade utility for source code... its not worth anything. Think about if you need to be able to access I-NET or ODBC connections without recompiling... if so make sure not to use the sqlstmtinfx and sqlstmtodbc classes (or whatever they are named) but the generic solution of creating the right statement type online. Oh, one really nasty thing (at least for me) was that in <=2.2 it didnt matter if you did stmt.getODBCErrorCode or connection.getODBCErrorCode after sending a statement. In 3.x it matters (which makes more sense, yes. Too bad I was stupid enough to use only the latter always... :<). > We have some custom classes that have to be converted too and I'm advised > that even some of the C needs rewriting. With 3.1 some of the C code will maybe need revision, yes. The stronger typing of C++ will maybe cause some minor problems. Problems can also arise if you use some special Windows API calls from your program. For example if you use GetModuleHandle() to find out if a program is running. The function is still existing but not acting like you expect it in a 32 bit context. Correcting these C problems shouldnt be a big thing as long as you still know what you are doing in your C code ;> > > Any help would be greatly appreciated... > > ta > John Regards, Dirk -- -- Dirk Gunsthoevel phone: +49 (0)251 624947 -- Hoeftestr.49 fax: +49 (0)251 624177 -- 48167 Muenster mobile: +49 (0)171 8047582 -- Germany http://members.aol.com/Plabit/welcome.html