I have added the ASCII import facility within my application using the OIWINEXEIMPORT_ASCII executable form and it works perfectly well within my development environment. When I use the RDK to create a runtime copy, and the runtime copy is tested, everything within that copy works OK except the ASCII Import facility: When the Import ASCII window is displayed, its title reads 'Failure to read resource record!Failure to read resource record' and this same message is displayed in a message box whenever I try to access any prompt within that window. Can someone help me please, is there a file I missed to copy or something I should have marked as publishable? </QUOTE> —- === At 08 DEC 1997 11:49PM Don Bakke wrote: === <QUOTE>Michèle, Can someone help me please, is there a file I missed to copy or something I should have marked as publishable? At the risk of suggesting something obvious, is the IMPORTEXPORT table available to this runtime system? dbakke@srpcs.com SRP Computer Solutions </QUOTE> —- === At 09 DEC 1997 09:09PM Michèle wrote: === <QUOTE>Although the IMPORTEXPORT table is flagged as publishable in the 'OpenInsight Tables' section within my OI for Workgroups SYSPROG, When the RDK is run it is not creating the IMPORTEXPORT table, and I cannot use the OIWINEXEIMPORT_ASCII executable form.

I also noticed that there is no dictionnary for IMPORTEXPORT in OpenInsight whereas it used to have one in AREV.

Any suggestions about how to transfer the IMPORTEXPORT table or how I can get OIWINEXE**IMPORT_ASCII to work in my runtime copy?

You need to have the IMPORT_ASCII_RESOURCE record from SYSENV copied in.

Create an application row repository entry as SYSENV:IMPORT_ASCII_RESOURCES and the next deploy should take.

For now, after create the entity, just check it in to the new system.

apk@sprezzatura.com

Sprezzatura Ltd

Michele, sorry about the late response. It turns out that for some reason OI does not deploy the IMPORTEXPORT table, though it is listed in SYSTABLES. I checked with our Marketing department to see if there was a licensing reason for this, but there was none; so it looks like something that someone forgot to do. Anyway, the work-around is to go into the System Editor, open the SYSENV table, open the RDK_DEPLOYTABLES record, and add the IMPORTEXPORT table to the list. This should solve your problems when you deploy your app.

This is an example of what should be typed in the RDK_DEPLOYTABLES ( IMPORTEXPORT ). Thanks for finding this for us. If you have any more questions please continue to post them on our web site, or call us here at Technical Support.

View this thread on the forum...