export action failed message

[Ted]

i have a2k and developed a simple two statement macro i attached to a
cmdbutton to let users export a table to their desktops. the mdb file is on a
shared network drive (called the "I" drive in its own folder).

the 'informational' message reads "Too many fields defined" and the "Help"
button opens to an empty grey screen (so no help).

the next thing you see is another window when you click 'Ok' which seems to
spell out the values of the terms in the macro command.

i'm going to list them out fwiw below:

macro name: Exporting
condition: True
action name: Transfer Spreadsheet
arguments: Export, 8, Screening Log,C:\Screening_Log,Yes,

note that the comma (",") following the "Yes" above is displayed in the said
message window.

anyone out there know that a2k is trying to tell me.

 

[Ken Snell [MVP]]

Try changing
C:\Screening_Log

to
C:\Screening_Log.xls

 

[Ted]

tried it but it doesn't like it. the same message as before only now the file
name reflects the added extention.

btw--what does that mysterious number "8" mean in the string. i don't seem
to see it anywhere else but the error message.

ted

 

[Ken Snell [MVP]]

The 8 refers to the version of EXCEL being exported (Excel 97, I believe).

How many fields are in the table/query named Screening Log?

 

[Ted]

i count 30.

The 8 refers to the version of EXCEL being exported (Excel 97, I believe).

How many fields are in the table/query named Screening Log?

 

[Ken Snell [MVP]]

Although this KB article speaks to saving a table, its "fix" may be what you
need to do with your Screening Log table:

http://support.microsoft.com/default.aspx?scid=kb;en-us;128221

 

[Ted]

this looks like it definitely offers the potential to do so.

much thanks, ken.

ted

 

[Ted]

i have been away from the project for a while...

it seems to me that the article's limitations are that it did not appear
relevant to my usage of the access 2000 version of their product (just up to
'97).

thanks, though.

t