Problem with Import Wizard in Access 2007 Runtime

[Mike n tx]

I'm getting an error when running the import wizard within Access 2007
Runtime. Specifically, when clicking the 'Advanced' Button to access the
import specs, I get a msgbox which says, "Advanced option not available.
This option requires the file acwzlib.accde to be read/write."

Because of the variable nature of the data to be imported, i'd love to be
able to use the import wizard and not have to write this code myself. The
import wizard is started using VBA >>> DoCmd.RunCommand acCmdImportAttachText.

It works on the source machine, when running Access in the full version and
runtime version. As far as I can tell, all permissions are set as open as
possible, and I'm running as admin on both machines. I have not tried it on
a third computer <yet>. The runtime db app is installed in Program Files.

Any Suggestions? Any help is appreciated.

Mike

 

[Jim Burke in Novi]

Do you not have a set specification that you could use? Seems to me that
users may not know how to use the wizard. I always create my specifications,
then run a macro or use DoCmd.TransferSpreadsheet. I prompt the user to
select the filename if that will be changing, then run the macro or the DoCmd
command. Do you have a situation where you don't know exactly what the specs
night be?

 

[Mike n tx]

Unfortunately, there are 3-5 different specs that might be encountered. I
could write a routine to do it all, but the Import wizard is very suitable
for my needs. I also use the Excel Import wizard, but haven't tried using it
with Runtime.

There seems to be an issue referencing the field names in the target table.
After the error msgbox I get a glimpse of the advanced form with the lovable
'#name?' in the first column of the first row.

 

[Jim Burke in Novi]

This probably isn't the suggestion you're looking for, but if I was in your
position, if you know the exact specs you'll need, I'd just define and save
them all, then have a combobox with two columns, one a general description of
each spec that the user could understand, another hidden column with the
actual spec name. Then I'd just use DoCmd.Transferspreadsheet, with the
selected spec name for the spec parameter. Once you do the initial spec
definitions (which with your method you'd be repeating every time you do an
import) and coding (coding should be pretty minimal) it would be very simple
from then on to just select the appropriate spec and click a command button
to do the import. Maybe there's something about your process I don't
understand that makes this less than desirable.

 

[Mike n tx]

Thanks for all of the input. I'll create the specs and use them in
TransferText methods. Now I'm just a little curious as to whether it can
actually be done the way I had originally planned.