MSYSCONF in QGPL type *FILE not found

[madhouse]

I have an MS Access database with a function to import a file from our AS400. This function has always worked until a few days ago. Now whenever I call this function it just hangs, and when looking at the QZDASOINIT job log there is a message which says MSYSCONF in QGPL type *FILE not found. My function in MS Access doesn't "touch" this file so why is it looking for it.

Just for your information here is the call to my function:

Call ImportODBCTable("ODBC;DSN=LIBINFOCBS11;UID=" & strUsername & ";PWD=" & strPassword & ";DATABASE=LIBINFO", "LIFLIPM", "LIFLIPM", acImport)

And here is the function which is does the importing:

Sub ImportODBCTable(ByVal strConnection As String, _
ByVal strSource As String, _
ByVal strDest As String, _
Optional ByVal intType As AcDataTransferType = acImport)

'intType = Transfer Type (acExport, acImport or acLink)
'strConnection = Database Name (full name including path of database to be imported)
'strSource = Source Name (name of object to be imported)
'strDest = Destination (name of linked object in database)

DoCmd.TransferDatabase intType, "ODBC Database", strConnection, acTable, strSource, strDest, False

End Sub


As I said before this has always worked until I installed the latest V5R2 Client Access Service Pack.

Does anyone have any ideas as to what could be wrong? Or can anyone suggest another means of importing the file from the AS400?

 

[blom0344]

" until I installed the latest V5R2 Client Access Service Pack."

Did you upgrade your client to V5R2 while still adressing a V4 AS400?

The MS Jet Engine seems to standardly look for an optional table called MSYSCONF, so it must be something at the MS side.

An alternative is to link the tables into Access and write table-make queries on them (also using Client Access ODBC)








T. Blom
Information analyst
tbl@shimano-eu.com

 

[madhouse]

T Blom - no I didn't upgrade to V5R2. I've had Client Access V5R2 installed on my PC for sometime now and it was only the latest Service Pack that I installed a few days ago.

I'll give you idea of creating linked tables ago and see what happens.

 

[madhouse]

Well I tried creating a linked table in Access to the file on the AS400 and although I'm able to view the records in the file it took almost half an hour to display the file which contains 3000 records. Also, it was almost impossible to page up and down through the table because it took an age just to do this.

So I'm at a bit of a loss - I even tried reinstalling Office 2000 in case there was a problem with MS Access and also tried reinstalling Client Access but that didn't make any difference.

Would be interested to hear if anyone else has got any ideas??

 

[blom0344]

Sorry,

I may have given you inadequate info on this.
Link tables in Access. Now create a tablemake query on the linked table and create a new table.
This should take seconds with just 3000 records.
Address the new table.
If you need this you can wrap all of this in a macro and activate from a form or use a little code......

Scrolling through linked tables is like scrolling through the output of a select query, i.e. far too slow

T. Blom
Information analyst
tbl@shimano-eu.com