CAPI Android Print Form

Discussions about creating CAPI applications to run on Android devices
Forum rules
New release: CSPro 8.0
Post Reply
diaznhugo
Posts: 18
Joined: December 1st, 2016, 7:24 am

CAPI Android Print Form

Post by diaznhugo »

Hello
I would like to know if there is a possibility to print the form in android format. I need to make a user manual of the complete form and has more than 300 questions.
Hugo Diaz Nuñez
Dominican Republic
Gregory Martin
Posts: 1777
Joined: December 5th, 2011, 11:27 pm
Location: Washington, DC

Re: CAPI Android Print Form

Post by Gregory Martin »

The only thing that you can do with CSPro is to use an undocumented tool with the following steps:

1) Run the ExportXMLMetadata tool, likely located here: C:\Program Files (x86)\CSPro 7.0\ExportXMLMetadata.exe

2) Select HTML.

3) Select your dictionary (extension .dcf).

4) Select your question text (extension .qsf).

Run the tool and you'll get an HTML file with the questions / response categories. This may not be exactly what you want, but you can open that HTML file in software like Word and then edit it in there.
szso
Posts: 17
Joined: January 10th, 2015, 5:26 am

Re: CAPI Android Print Form

Post by szso »

Dear Gregory,

It does not work with dictionary with multiple records. Is there another way to do it?
Thanks
Gregory Martin
Posts: 1777
Joined: December 5th, 2011, 11:27 pm
Location: Washington, DC

Re: CAPI Android Print Form

Post by Gregory Martin »

I'm surprised that the ExportXMLMetadata tool doesn't work. Can you send your .dcf/.qsf files to cspro@lists.census.gov? We can see why it is not working.

Other than that, the only way to accomplish your task is to write a custom tool yourself to do this.
szso
Posts: 17
Joined: January 10th, 2015, 5:26 am

Re: CAPI Android Print Form

Post by szso »

Dear Gregory,

Dictionary and qsf files just sent right now.
szso
Posts: 17
Joined: January 10th, 2015, 5:26 am

Re: CAPI Android Print Form

Post by szso »

Gregory,

The issue has been fixed thanks to your support.
It said it was related to some characters in the dictionary file and it was fixed using the 7.1 beta version.

I am glad to have it working in the next official release.
Thanks for your support.
Post Reply