Hi.

I have a program that is somehow behaving different on my own developer PC than it does on the server where it is supposed to run. On the server, the last object of a COblist will not be updated in the DB, but if the program is run locally on my PC the last object is updated just fine. The server is running Win2000 Server and my PC is WinXP Pro. The EXE is build with MFC as a statically linked library.

Anyone have any suggestions on what this might be?

I don’t think the location change can be
held responsible here. The way you are
connecting to the database, may be a hard coded
path is raising an exception somewhere that’s
causing some process to get terminated
prematurely and your database not getting updated.

Certainly some code or the database info and
a bit more info on what you are doing would help
immensely to understand the problem better.

Thanks for swift reply.

Unfortunately the program is not my own writing, and the concerning code is scattered around so many places that I don't think a posting of the code would help you mutch (and mutch of the code is written in norwegian, so it would be hard for you to understand).

Anyway, what the program does is to take an EDIFACT-file (PRODAT message used in the Nordic power market), strip the information in the file down on plant-level, and then update a DB accordingly. The individual plant-information from the file is stored in plant objects in a COblist prior to updating the DB. Depending on if the plant-objects are already present in the DB or not, the plant gets updated. A logtable in the DB contains info on each plant in the EDIFACT-file ( a plant gets a -1 if not updated, 1 if updated). The problem is that the last plant will sometimes get updated and sometimes not updated if the program is run on the Server. If I run the program on my PC all the plants are always updated. I use the same EDIFACT-file to test on both computers, and it is the same EXE file being executed.

I have begun wondering if it might have something to do with the version of MDAC running on the computers. The server is running MDAC 2.6 RTM and my PC is running MDAC 2.7. Anyone know if an upgrade of the MDAC version might help?

 Your suggest that MDAC may be the likely culprit is most probably correct or at least along the right path. If you are moving it from the development environment to a production box their are a number of things that you should probably check; are you accessing the same data-store? Perhaps what you are witnessing is the manifestation of different DBMS default behaviours, or perhaps one has been specifically configured / has a different set of integrity rules / something of that nature.

Regards,
Meredith Shaebanyan