https://community.hpe.com/t5/operating-system-microsoft/access-2000/m-p/2792775#M1979 I'm not too hot on informix and you may well have to contact the informix user group (<A href="http://www.iiug.org)" target="_blank">www.iiug.org)</A> if this doesn't work.<BR /><BR />The problem may be due to your VBA code using references that Access 2000 (or access 9 as it really is) doesn't understand. To add extra reference libraries, go to the Visual Basic editor and click on Tools &gt; References. Try adding the following<BR /><BR />Microsoft DAO 3.6 Object Library<BR />Microsoft Excel 9.0 Object Library<BR />Microsoft Visual Basic for Applications Extensibility 5.3<BR /><BR />See if this is of any use. Bear in mind Access 2000 still won't understand some VBA commands (such as Error, which needs to be replaced by Err.description).<BR /><BR />If anyone out there knows of a knowledge base article that covers 97 - 2000 upgrades, please let me know cause i had to learn this myself and would like to have the official version.<BR /><BR />HTH<BR /><BR />Patrick<BR /><BR />P.S. Of course you need to try all this on a backup database rather than your live version ;) Fri, 23 Aug 2002 12:20:02 GMT Patrick Ruane 2002-08-23T12:20:02Z https://community.hpe.com/t5/operating-system-microsoft/access-2000/m-p/2792774#M1978 We were using access 97 as front end and for saving the record we used acCmdSaveRecord instrinsic menu function. Usage is <BR />doCmd.RunCommand acCmdSaveRecord.<BR /><BR />We migrated from access 97 to access 2000, acCmdSaveRecord is not inserting record into informix database where the datatype of one of field in the table is of SERIAL datatype. <BR /><BR />Anybody can help to resolve this. Fri, 23 Aug 2002 11:49:23 GMT https://community.hpe.com/t5/operating-system-microsoft/access-2000/m-p/2792774#M1978 Sivaji 2002-08-23T11:49:23Z https://community.hpe.com/t5/operating-system-microsoft/access-2000/m-p/2792775#M1979 I'm not too hot on informix and you may well have to contact the informix user group (<A href="http://www.iiug.org)" target="_blank">www.iiug.org)</A> if this doesn't work.<BR /><BR />The problem may be due to your VBA code using references that Access 2000 (or access 9 as it really is) doesn't understand. To add extra reference libraries, go to the Visual Basic editor and click on Tools &gt; References. Try adding the following<BR /><BR />Microsoft DAO 3.6 Object Library<BR />Microsoft Excel 9.0 Object Library<BR />Microsoft Visual Basic for Applications Extensibility 5.3<BR /><BR />See if this is of any use. Bear in mind Access 2000 still won't understand some VBA commands (such as Error, which needs to be replaced by Err.description).<BR /><BR />If anyone out there knows of a knowledge base article that covers 97 - 2000 upgrades, please let me know cause i had to learn this myself and would like to have the official version.<BR /><BR />HTH<BR /><BR />Patrick<BR /><BR />P.S. Of course you need to try all this on a backup database rather than your live version ;) Fri, 23 Aug 2002 12:20:02 GMT https://community.hpe.com/t5/operating-system-microsoft/access-2000/m-p/2792775#M1979 Patrick Ruane 2002-08-23T12:20:02Z