Community
Showing results for 
Search instead for 
Do you mean 
Reply

APFW - Error "This command is not available because no document is open"

Copper Contributor
Posts: 83
Country: Australia

APFW - Error "This command is not available because no document is open"

Using APFW 2013 SP1 and IE 10

 

Customer has been trying to run a adt template from the web browser and it appears that if the template has a table in it will throw up the error "This command is not available because no document is open".  I have tested with other templates that do not have a table and work correctly.  I have also tested these templates that do not open from the browser in the desktop version and works as expected.

 

The customer has application forms they have auto filling info from act! and staff member does not have access to the desktop version.  Has anyone come across this issue before?  Any ideas how to resolve?

 

2013-11-20_16h54_51.png

 

Thanks

Damon

Moderator
Posts: 722
Country: USA

Re: APFW - Error "This command is not available because no document is open"

This issue can be caused by invalid images or tables in the template. For more information, refer to the following Knowledgebase article:

 

http://kb.swiftpage.com/app/answers/detail/a_id/34333

Elise O'Pry
Swiftpage
Visit our knowledgebase at http://kb.act.com
Copper Contributor
Posts: 83
Country: Australia

Re: APFW - Error "This command is not available because no document is open"

Thanks for the reply.

 

Step 3 is to remove the images and tables.  It then indicates to test the template to find the offending image or table.  But says nothing about re-adding the tables.

 

Does this mean we can not have tables in a template if it will be used by APFW users?

 

Cheers

Damon

Moderator
Posts: 722
Country: USA

Re: APFW - Error "This command is not available because no document is open"

There shouldn't be a problem with having tables in the template, however the particular table in question may be causing the error. You may try to add the table back and test to see if it still gives the error message.

Elise O'Pry
Swiftpage
Visit our knowledgebase at http://kb.act.com