Auto-Detect Form Fields from Word 2007

LiveCycle 8.x fails to detect form fields from form documents I've created in Word 2007. I also notice that Word 2007 documents saved as Word 2003 documents do not convert the text fields either (text fields static).
Is LiveCycle 8.x compatible with Office 2007 or does it depend on the conversion from 2007 (.docx format) to 2003 (.doc format) before creating the PDF then detecting and placing the fields?

I could tell it not to run in Acrobat 9 but can’t figure out how to do that in version 11. When I use the Create Form command, I get a series of windows that guide me through the process of creating the form. Unlike Acrobat 9, none of those windows includes an option for not running auto detect. At the end of the process, the form is created with fields. The only solution seems to be to let Acrobat create the fields, and then delete them all and manually create the fields I want. Thanks for your feedback.

Similar Messages

The "auto-detect form fields" function.

Is it the same in adobe 11 as it is in adobe 9?

I could tell it not to run in Acrobat 9 but can’t figure out how to do that in version 11. When I use the Create Form command, I get a series of windows that guide me through the process of creating the form. Unlike Acrobat 9, none of those windows includes an option for not running auto detect. At the end of the process, the form is created with fields. The only solution seems to be to let Acrobat create the fields, and then delete them all and manually create the fields I want. Thanks for your feedback.

Auto-generate form fields from PDF in LiveCycle?

I have a PDF created with InDesign that is destined to be an interactive PDF form. For previous versions I have imported it into Acrobat and had it generate the fields based on the text columns I layed out in InDesign.
I wanted to try for more function in my form, so I thought I'd use LiveCycle, but I can't figure out how to get it to automatically create form fields when I first import the PDF. Is this not something that LiveCycle does, or am I just missing something?

Hi,
I don't like automatically generated PDFs.
But sure you can create this with the LCD. The only thing is that the acrobat recognize lines (for example) and place a textobject to this location. The LCD not really.
Open the LCD
Then select "New Form".
Then select "Import PDF".
Then select "Create"
Then the software will try to recognize everything..
My opinion is - THE BEST WAY to create a formular is this to create by myself in the LCD step by step. Then this software has so many possibilities...for really good PDFs.
Kind regards Mandy

Is there a sensible way to import form fields from an old pdf into a new pdf?

I'm working with Acrobat X Pro on a Windows PC platform. I've been working with a file that was originally created in CorelDraw X3, in landscape orientation. That document was then saved as a pdf and set up with many form fields (it's an order form). The document needed to be updated with minor changes made in the Corel file. I resaved as a pdf and now want to transfer the existing form fields from the old document into the newly revised one. I've tried copy/paste, but have to do small sections at a time because the program doesn't let me bring in all of the fields at the same time. I then tried Document > Replace page, which I've seen described in other forum posts; but when I do that, the entire set of fields comes in rotated at 90 degrees counterclockwise. I did read that if the original document was created in a different orientation, that could affect how the fields paste in, but that is not the case here. The original file, and all successive pdf files all have been the same orientation. I'm boggled and think that there has to be an easier way than copying fields, a section at a time, and resizing them all over again.
This older post is pretty similar to what I am trying to do, but it seems I'm getting a different end result. Any suggestions?
Create fillable form with changing source document

I am using Acrobat Pro 10. I have the same problem and finally after numerous different attempts of solving based on all the suggestions, I resolved my problem by Printing to PDF via the print dialog in Word. When I pasted the fields that were previously rotating onto the new "printed" PDf, the fields retained their orientation as desired.
To clarify, I am using Word 2007, Acrobat Pro 10, the document is landscape, both the original (with fields) PDF and all attempted new PDF's were of the diemnsions 11 x 8.5. The only noticeable difference in the PDF properties for the PDF's were Tagged PDF and Fast Web View. The original PDF (with fields) was No in both cases and all attempts other than the Print to PDF were Yes, meaning that the Print to PDF was No. I am not sure if this made the Print to PDF work or not as I have already spent too much time trying to resolves this issue. Hope this helps.

Detecting Form Fields

Here at work, we use AutoCAD to draw up specs on our products. From there we convert to .PDF where we fill in the text fields as needed for our products.
Rather than manually placing each text field on the PDF, how do I have the program locate where the fields should go? I think this is called, Detecting Form Fields.
I have my PDF I just created from AutoCAD with no text fields in it yet.
I go to Forms > Add or Edit Fields, then I get a pop up saying, "Currently no form fields in this PDF. Do you want Acrobat to detect fields for you?"
I click YES and it says, "No new form field annotations were detected"
How do I get this to find the fields so I dont have to manually insert every text field??
I am using Adobe Acrobat Pro 9.5
Any help is appreciated.
Thanks,
Dan

Here are some guidelines: http://acrobatusers.com/tutorials/designing-forms-auto-field-detection-adobe-acrobat
But if you can't change the source document design so that the Form Wizard is able to divine where fields should go, there's not a lot you can do.

Bug? Accessibility Tags Converting from Word 2007

This seems like a minor issue, but it's one that could create a lot of frustration for a disabled person using a screenreader to read tabular data in a PDF.
As you know, Acrobat plays nicely with Office apps allowing users to create tagged (structured), accessible PDF documents from MS Office files. I just created a simple docx file with a table (attached), and when I converted it to PDF, I noticed a difference in the tags it creates compared to conversion from Word XP. As you see in the Word file, the table is very basic, except that one of its column headers is split into two cells. This is actually a very common technique for presenting table data. In order to automatically tag the header rows as table header cells <TH> in the PDF, I set the first two rows to "Repeat Header Rows."
Converting from Word 2007 with the "Save as Adobe PDF," or any other method that uses the Acrobat plugin, creates a tag tree that is missing a <TH> tag. I found the problem when I was testing a file with JAWS screenreading software. Using the JAWS "current cell" command (Ctrl-Alt-Numpad 5) to announce the column headers. It reads the wrong header for the current cell due to the missing <TH>. So, in my example file, it announces $2 and $5 as 2010 amounts rather than 2009. That could be pretty confusing to a screen reading user, to say the least.
I then compared the result to the new Word 2007 "Save as PDF or XPS" feature. That feature tagged the file properly and the header columns match up.
Compare the attached "save-as-adobe-pdf.gif" to"save-as-pdf-xps.gif". Note the empty (but necessary) <TH> tag in the latter image.
Just as a sanity check I had a coworker with Word XP convert the file. Those tags were correct too. So, this must be a problem between Acrobat and Word 2007.
Anyone have other observations on this? I'm going to be leading some accessibility training and right now, it looks like using the Word 2007 conversion feature is the way to go.
I'm using Acrobat 9 Pro.
Thanks,
Joe

Hi Joe,
I sense your frustration. For any organization that has to or wants to engage in providing accessible online information
a serious logistics support issue raises its head. To do PDF, HTML, whatever the proper way (and it can be done)
requires more resources (training, knowledge, hardware, software, changes to work flows, perhaps some more staff).
The is no "work smarter with less & pump out more" in this venue.
Yes, it is helpful (and necessary) to "be one" with the S508 "paragraphs" - WCAG 1.0 - WCAG 20.
However, once anyone begins to provide PDFs that must be "accessible" the first, single most important reference is ISO 32000.
The Adobe PDF References that preceded PDF becoming an ISO Standard are useful; but, ISO 32000 is the standard.
In this documentation there is full discussion of what *must* be done to provide an accessible PDF.
Without a firm understanding of this content, other information tends to bring about a defused opacity of focus which can
contribute to major conceptual errors vis-a-vis accessible PDF.
Leonard Rosenthol's AUC blog entry provides a link to the ISO permitted Adobe version (free) of ISO 32000-1.
http://www.acrobatusers.com/blogs/leonardr/adobe-posts-free-iso-32000
Additional, useful information is found in these two documents:
(1) - PDF Accessibility API Reference (from the Acrobat SDK)
https://acrobat.com/#d=J7bWW4LvNoznh8fHCsfZDg
(2) - Reading PDF Files Through MSAA
https://acrobat.com/#d=uIOvkVTP74kag3bXFJLIeg
About JAWS - Yes, much used. However, not the exlusively used AT application.
If I use Windows Eyes, NVDA, a braille reader, or something else then what?
JAWS *does not* define "it is accessible"...
re: (1)
"Game away and if it ...."
   Consider "Stop before right on red".
   "Compliance" is Stop on Red - Turn Right
   "Intent" (aka usability) is Stop on Red - Look Good for on coming traffic that has the right of way - Yield - when clear, turn right.
But, at least we are not talking about "left on red" 8^)
re: (2)
Just an observation. A defective product that claims to be "whole" can get entities (individuals/businesses) into a sticky wicket.
Putting a high volume of defective products on one's selves only increases the probability that one gets 'busted'.
Quantity replacing Quality just is not a success precursor.
Case in point - Target and the national class action legal action that was taken against it with regards to "accessibility" of online information/services.
Resolved now - see NFB's web site.
re: (3)
Ah, but what would Judge Judy or Judge Marily say?
Efficiency does not preclude providing a "whole" product.
I doubt that there will ever be a seamless "one-click" between products of any of the dominant software houses.
They are intense competitors. That this is the case does not abrogate others from providing a "whole" product, no?
So, if the organization wants the "we do accessible PDF" label then it pays the freight - Adobe Pro, training, appropriate work flows, etc
that permit delivery of PDFs that meet the standards for what a well formed tagged output PDF is (accessible is a sub-set of this).
For PDF there is no other way.
If this cannot be done then there is always HTML as an acceptable method (to some it is the preferred and only "true" way).
However, HTML, done "right" for accessiblilty is just as demanding in its own way.
With each AT version / dot version release, JAWS - Windows Eyes - NVDA & others hone in closer on utilizing PDF ISO Standard 32000.
That means if you deploy "accessible" PDF you need to provide PDF that live to the ISO standard.
Keep in mind that S508's paragraphs began when, effectively, HTML was "it". In software terms that was geologic eons ago.
For contemporary AT to effectively parse PDF, the PDF must be a well formed Tagged PDF having a format/layout that reflects a logical hierarchy.
Creation of all this must start in the authoring environment with the content author.
The post-process PDF output then assures that the PDF elements (tags) are the correct type, have the requisite attributes, etc.
Without this, AT will not be able to provide the end-user effect utilization of the PDF.
So, for AT to properly 'work' the PDF, <TH> elements *must* have the Scope attribute's value defined, Row and Column Span values defined, etc.
Scope, Row Span, Column Span, Table IDs and Headings must be added as part of the post-processing of a PDF using Acrobat Professional.
An alternative is the Netcentric CommonLook plug-in for Acrobat Professional. What it does, Acrobat Pro can do; however, the CommonLook
provides a robust user interface. Downside: at some $1k per seat it is not 'cheap' and it has a *steep* learning curve (Sitka Pass?).
Two table related resources are at this AUC thread (in post 3 and 4). They may be of some usefulness.
http://www.acrobatusers.com/forums/aucbb/viewtopic.php?id=23178
When the "smelly stuff" gets feed into the maw of the fan it's prudent to not be directly down stream, eh.
Consider Target and the situation they put themselves in.
Consider submittal of accessible PDF to fedgov or stategov agencies.
They won't be in front of the fan if usability of the PDFs becomes an issue.
Rather, it will be those submitting. After all the agency did say "accessible".
Better to slow down and do it right or ramp up resource loading to support "schedule" than to stake oneself out as someones "feed" tomorrow, no?
In the final analysis, for PDF, HTML, or any 'format', Accessibility is the Usability + Compliance.
Does it take improvements in professional development/training, adequate hardware/software, *time*?
Yes. But, it all comes down to "where the rubber hits the road" - what tires are you on?
It can be done. I do it one small step at a time every day. Often, that's what it takes.
Deliverables are provided; but, with no mis-labeling and the incremental progress is identified, celebrated and the whole thing continues until
the "road" is completed properly.
Don't want wash outs, bridge collapse or what not tomorrow <g>.
(But then I'm a fan of "Holmes on Homes" which may go a long way towards understanding my point of view when it comes to accessible PDF.)
re: function(){Return ....
Good question.
My guess - either from the cut & paste I initially performed from the application I'd been using to assemble write up and screenshots or something associated with the Adobe Forum application.
It can't be that I'm 'special'; if that was the case one of my occassional lotto quick picks would have been a big $ winner long ago <G>.
fwiw -
You'll find a number of "Accessible PDF" related resources in the threads at the AUC Accessibility Forum.
http://www.acrobatusers.com/forums/aucbb/viewforum.php?id=18
Two Accessible PDF related on demand eSeminars are also available.
Look for Duff Johnson's and Charlie Pike's (on page 2) eSeminars.
http://www.acrobatusers.com/learning_center/eseminars_on_demand
Be well...

Convert from Word 2007 to Acrobat Pro 9; bookmark issue

When converting from Word 2007 to PDF using Acrobat Pro 9, enabling "Convert Word Headings to Bookmarks", not only are Headings converted to bookmarks, but bulleted text (styles), as well. I attached the subsequent PDF, but this forum does not permit the document attachment. I really only want to show the Headings. (It may be noteworthy to mention that when using this same set of styles in Word 2003 and Acrobat Pro7 the conversion was seamless.)
Does anyone know how to correct this? I have reviewed my Word styles and the issue does not appear to be on the document level. Am I missing some obscure setting?
I'd appreciate any help.
Thanks.
-PS

I had a similar situation occur when converting Word 2007 docs to Acrobat Pro 9 Extended via the PDFMaker (Acrobat add-on tab in Word 2007), and I want to share a workaround. In summary, I had extraneous bookmarks appear in the PDF (heading 3s, body text, XE Index tags, etc.) that I did not select to be in the PDF. I contacted Adobe's support and ended up talking for approx. 2.5 hrs to 2 different reps with no solution. They reproduced the issue on their end, but couldn't figure out how to fix this. I recently upgraded to Tech Comm Suite 2.5 from 1.0. The Word 2007 conversion to PDF via Acrobat Pro 8.x worked fine.
Scenario: I have 400-page user guides that I am required to publish as 'Press Quality' with navigable bookmarks to certain headings in the PDF. I have to generate the PDF via the Acrobat Add-On tab in Word, since I do not want to manually insert bookmarks in the PDF for 400 page documents (as you would when using the Adobe Print driver or 'Save As PDF' operation).
In the Adobe PDF Maker dialog, I have the following Application Settings selected in the General tab:
Create Bookmarks
Add Links
In the Bookmarks tab, I originally had only two Elements selected for bookmarks:
Heading 1 (a Word Heading already present) as the Level 1 Bookmark.
Table of Contents Bookmark (a Word Style I created) as the Level 2 Bookmark.
As a result, the Convert Word Headings to Bookmarks and Convert Styles to Bookmarks were both enabled in the Bookmarks tab.
The resulting PDF contained extraneous bookmarks that I did NOT select, such as Heading 2s, 3s, even body text - too much to clean up for 400-page documents! Additionally, and this was annoying too - I noticed that all bookmarks appeared as Level 1 Bookmarks, making the PDF Bookmarks really messy. I converted multiple Word 2007 documents with the same results.
How I resolved the issue:
In the Word 2007 document, open the Styles window, select all instances of the specific Word Heading (in my case, Heading 1). All instances of the selected Word Heading will be selected in the doc.
Click the New Style icon in the lower left part of the Styles window.
In the Create New Style from Formatting dialog, create a new style name (e.g., I created H1).
Just to be sure to NOT create the new style from an existing Word Heading, I selected (no style) in the Style Based On field.
Configure the remaining formatting items as necessary, and then click OK. All of the selected instances from the old Word Heading style are now changed to the new style created (in my case, H1).
Click the Preferences tab in the Acrobat add-on tab in Word 2007, and open the Bookmarks tab.
Remove the old Word Heading (in my case, it was Heading 1) so it no longer will be included as a Bookmark in the PDF.
Select the new Word Style that you created (in my case, H1) to be generated as the Level 2 bookmark. Note: My original Level 1 bookmark, "TOC Bookmark," is still selected. Now, only the Convert Word Styles to Bookmarks is enabled in the Bookmarks tab.
Generate the PDF once again via the PDFMaker, and no extraneous bookmarks appear in the PDF.
Note: I also noticed that when Index tags (XE tags) were present in an element selected to be a bookmark in the PDF (such as my new style, H1), they also appeared in the PDF Bookmarks pane. I just moved the XE tags down to the body text so they would no longer appear in the PDF.
Question for discussion: Maybe there is a bug in the PDFMaker when both Convert Word Headings to Bookmarks and Convert Styles to Bookmarks are selected? The extraneous bookmarks do not appear in my PDF when only Convert Word Styles is selected.

Exporting acrobat fields into Word 2007

Hi all,
I have a client who had an adobe document on his website which user fill out and then submit using Outlook. He now wants to create a form letter (in Word 2007) by using the data that the users submitted on the acrobat document.
In a nutshell, I have to export the adobe fields into Word. Being a total novice, I don't even know if this is possible?
I am thinking along the lines of some sort of a mail merge.
Thanks in advance.

Have you exported in the various formats and examined the created file?
FDF and XFDF are special formats for Acrobat forms.
Text is a text with tab delimited. The field names comprise the first row and each form's data is then listed under the first row in the same order as the field names in row one.

I have had a trial version of Acrobat X1 Pro - I have decided not to buy at this stage - for some time it has been conflicting with opening PDF docs after saving as from word 2007 - I uninstalled Pro X1 and now when I save as from word 2007 to PDF it will

Can anyone help with this - do I have to uninstall Reader and then reinstall?

I have had a trial version of Acrobat X1 Pro - I have decided not to buy at this stage - for some time it has been conflicting with opening PDF docs after "saving as" from word 2007 - I uninstalled Pro X1 and now when I "save as" PDF from word 2007 to PDF it will save the document as a PDF but will not open the document to display after publishing - I have to got to where the file has been saved to view the new PDF document - this is really annoying - do I have to delete adobe reader and reinstall it - adobe needs to look at this conflict with acrobat pro as I have even gone it to properties and tried to have adobe reader as the default PDF program - the main issue is that I cannot view the PDF after publishing it from word 2007

Acrobat Pro 9 - Conversion Error from Word 2007

I do not want to hijack the thread or question raised by another poster a short time ago but I cannot figure out how to correct the below.
Office 2007 fully updated
Vista 32-bit
Acrobat Pro 9.3.4
I have to provide data for someone else to assemble and publish and have been attempting to convert some Word documents nearly full of tables to press quality .pdf. Whenever I try the conversion, Acrobat Pro seems to re-center the tables both horizontally and vertically forcing the misalignment of the rows of data although any repeating headers remain properly placed. I can even see the table shift downward slightly when using the Acrobat conversion macro within Word. It may be adjusting the margins instead of re-centering.
I have tried using the macro within Word 2007, Create PDF within Acrobat Pro and Print to PDF as well as tweaking some of the settings such as lowering resolution and turned off unused settings such as enable fast web view, etc. The glitch also occurs with High Quality Print. Standard used to work but after the update to 9.3.4 that conversion shows the same problem. I even tried saving in Word 97-2003 format with the same results.
The documents in question do have custom page sizes and margins but do not use any abnormal fonts. I have tried changing the margins but the conversion to .pdf still changes the information and/or magins as described above. Row height seems to be correctly maintained.
I realize that a knowledgeable user can export the .pdf back into Word or other program but am trying to make it more difficult for someone to edit information which has always had extremely negative consequences in terms of data organization, layout and even integrity.
There has to be something really silly that I am overlooking.
Thank You

Thanks Bill.
Sorry for the delay, Verizon dumped its DSL +service to Frontier so we had one of the bi-weekly extended outages.
No changes occurred when I changed the default printer to Adobe PDF. All of my printers are new enough so that they can handle the current margins so I do not think that they is a problem there but changing the default as suggested by you and Michael eliminates that as the source.
I had previously been able to convert using the built-in converter in Word but was unsure whether or not the result would be press quality and was unable to find this information in my searches. I retested this and conversion using Word’s built-in converter works without a problem.
The conversion using Combine Miles > Merge Into A Single PDF also works without a problem with the highest quality setting. It took several hours to run but I guess or assume that it was because of the number of tags as this is a quick setting and therefore I could not disable the tagging which is not needed in this case.
I was also able to convert the same file which had been saved from Word 2007 into the 1997-2003 format as described above but the same problem came up when using the Acrobat macro and Create PDF from File. I had even created a modified press quality settings to modify settings like disabling autorotate, Object Level Compression, changed the binding option, lowered resolution, bumping the format up to PDF 1.7, etc., but all produce the same result. I have tried changing the document margins in case the conversion process rounded these but all produce the same artifact/problem except when I use Combine Files or the converter built into Word.

Acrobat Pro 9.1 no longer creates PDFs from Word 2007

I upgraded from Acrobat 7 to 9 specifically to gain more control over settings when making PDFs from Word 2007. This worked as I had hoped until the 9.1 vulnerability upgrade was installed. Now it will no longer create PDFs from Word 2007 documents at all.
From within Word 2007, when I click on "Create PDF" (whether in the Office menu or Acrobat toolbar) it asks for a file name, but after I click "Save" does nothing. This is true even for the simplest possible document, using the "Default" settings for PDF "Preferences."
If I right click the file name of the document in Windows Explorer, with Word 2007 closed, and click on "Convert to Adobe PDF" in the menu, it starts and the staus box comes up, but after a few seconds quits and displays "An unexpected error occurred. PDFMaker was unable produce the Adobe PDF."
I can still "Save As" PDF in Word 2007, but this gives me little control over the format.
Is there any way that I can get Acobat 9.1 to do what I bought it for, and what Adobe advertises it will do?

Try printing to the Adobe PDF printer, the more fundamental process (PDF Maker is a preprocessor for the printer). If that does not work, then try with print-to-file selected. Open the file in Distiller and see if the PDF is created. If the latter happens, then check for AcroTray running in the background. It is required to automate the process and is needed by PDF Maker.

The numbering format keeps changing when making PDF's from Word 2007 ? Using Acrobat 9 Pro Extended

The numbering in (Contents) format keeps changing when making PDF's from Word 2007 ? Using Acrobat 9 Pro Extended.

The issue is that I have made up a contract in Word.
The second page has a list of all contents of the contract.
gghhjhhbhbhhbhbjbhj....1
bv v vghvjvjnnnnnnnnn....2
When we convert to PDF some of the numbers change. Example 20 becomes 201.
Your help is appreciated.
Cheers Ocean designs.

Acrobat guide disappeared from Word 2007 panel

Hi,
The Acrobat guide disappeared from Word 2007, but still ok on others Office 2007 sw. I´ve already tried to active Acrobat COM at Word Supplement, but without success. Hope that someone can help.
Tks

Michael,
Tks for you help. It soved other minor problems with my Acrobat, but the problem wtih the Word remains. By "guide", I mean those button on the top of the screen, i.e. "File", "Edit", "Developer". It use to have a extra "guide" named "Acrobat", which disappeared from the Word, but stills ok in the others Office sw.
Thanks anyway.

Fast Web View breaking links/bookmarks in PDFs from Word 2007

I'm running Acrobat Pro 8.1.2 on WinXP, and I recently noticed an issue with PDFs that I'm creating from Word 2007. If I turn on the setting "Save As optimizes for Fast Web View," any links or bookmarks in the file break when I do a Save As. If I turn the setting back off, Save As doesn't break them.
I had had problems creating the PDFs using the PDFMaker plug-in for Word, so I used the Save As PDF or XPS feature from Microsoft instead.
PDFs created using FrameMaker are not giving me problems.
I don't know whether this is related, but the Settings button on the Save As dialog box is no longer active. I'm sure I was able to click it before, but I can't now. And that goes for PDFs from Word or FrameMaker.
Anyone have any clues?
===========================================
Rick Henkel
http://rickhenkel.googlepages.com/index.htm

This is related to a bug in the direct PDF output from Word 2007. I was told that Microsoft has fixed this bug in the final SP2 release (so when the service pack becomes available, this problem will not be present).
Until then, the workaround is indeed to turn off the "Save As optimizes for Fast Web View" preference in Acrobat (Edit > Preferences > Documents, under Save Settings).
Shlomo Perets
MicroType * http://www.microtype.com
FrameMaker/Acrobat training & consulting * FM-to-Acrobat TimeSavers
"Improve Your FrameMaker Skills" live web-based training sessions

Posting to a blog from Word 2007 or Word 2010 with pictures

Ok, this works fine SharePoint2010 with both Word 2007 and Word 2010.
When I try to publish a post that has pictures in it to a SharePoint2013 blog from Word 2007/2010 I get an error stating 'word cannot publish the pictures in this post'. This happens weather I use 'Launch blogging app' from the SharePoint2013 'Blog tools'
menu or launch Word2007/2010 independently and publish from there. I presume I have setup the 'Manage accounts' section to publish to the blogs correctly as the 'Picture' options do say 'SharePoint blog'.
Using SharePoint2013 'Create a post" option works just fine with images also.
This is quite maddening as I am trying to set up test cases so my agency can decide on SharePoint2010/2013. The users appreciate the ability to use the tools they are familiar with to create the blog entries (Word2007/2010) in SharePoint2010 and it is not
a confidence booster when I cant get SharePoint2013 to work.
I have installed both SharePoint2010 and 2013 on independent virtual machines to testbed. I used practically all the default settings.
Any ideas or options for me?
I would be willing to deal with some type of paid support incident if that is how this must be resolved.

here is the example f international Characters : ÅÄÖ or something like Jon
Löh....
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Auto-Detect Form Fields from Word 2007

Similar Messages

Maybe you are looking for