 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWordDirectoryUser Groups Related Topics Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ... |
MS Office Forum / Word / Mailmerge and Fax / May 2008Merging Time Fields
My data source has the time formatted in this manner: 08.30.00 and I want it to print 8:30 am in Word yet it prints 12:00 am. If the time is 13.30.00, it will print fine: 1:30 pm. What is wrong?  SignatureKim Try adding a \@ "H:mm" switch inside the closing } of the mergefield that is displayed when you use Alt+F9 to toggle on the display of the field codes SignatureHope this helps. Please reply to the newsgroup unless you wish to avail yourself of my services on a paid consulting basis. Doug Robbins - Word MVP > My data source has the time formatted in this manner: 08.30.00 and I want > it > to print 8:30 am in Word yet it prints 12:00 am. If the time is 13.30.00, > it > will print fine: 1:30 pm. What is wrong? Does not work. 13.30.00 will print correctly as 13:30 but 08.30.00 prints 0:00 It's treating these values differently. SignatureKim > Try adding a > [quoted text clipped - 8 lines] > > it > > will print fine: 1:30 pm. What is wrong? From the Tools menu in Word, select Options and then go to the General tab and check the box against the "Confirm conversions at open" item. (In Word 2007 it is Office Button > Word Options > Advanced > General > Confirm file format conversion on open). Then when you attach the data source to the mail merge main document, you will be given the option of using the DDE method of connection which should read the data as you have it formatted in the table. Signature<>>< ><<> ><<> <>>< ><<> <>>< <>><<> Graham Mayor - Word MVP My web site www.gmayor.com Word MVP web site http://word.mvps.org <>>< ><<> ><<> <>>< ><<> <>>< <>><<> > Does not work. 13.30.00 will print correctly as 13:30 but 08.30.00 > prints 0:00 [quoted text clipped - 23 lines] >>> -- >>> Kim My data source is a .txt file, it's generated from another application. I tried all 3 DDE options available: Excel, Access, and Query, and none of them work SignatureKim > From the Tools menu in Word, select Options and then go to the General tab > and check the box against the "Confirm conversions at open" item. (In Word [quoted text clipped - 30 lines] > >>> -- > >>> Kim I cannot replicate your problem using { MERGEFIELD "Start" \@ "h:mm am/pm" } { MERGEFIELD "Start" \@ "h:mm am/pm" } and a tab delimited text file containing Start Finish 08:30:00 09:25:00 12:30:00 13:30:00 15:30:00 16:00:00 as the data source. The result for the first record is 8:30 AM 9:25 AM The connection to the datasource was the default method of connection. SignatureHope this helps. Please reply to the newsgroup unless you wish to avail yourself of my services on a paid consulting basis. Doug Robbins - Word MVP > My data source is a .txt file, it's generated from another application. I > tried all 3 DDE options available: Excel, Access, and Query, and none of [quoted text clipped - 40 lines] >> >>> -- >> >>> Kim Post an offending sample of your data - like Doug I cannot reproduce the fault on the basis of the information you have provided. DDE is for Excel/Access, TXT should not be an issue. Signature<>>< ><<> ><<> <>>< ><<> <>>< <>><<> Graham Mayor - Word MVP My web site www.gmayor.com Word MVP web site http://word.mvps.org <>>< ><<> ><<> <>>< ><<> <>>< <>><<> > My data source is a .txt file, it's generated from another > application. I tried all 3 DDE options available: Excel, Access, [quoted text clipped - 43 lines] >>>>> -- >>>>> Kim The time field in my text file is formatted like this: 08.30.00 13.30.00 separated by decimals not colons. SignatureKim > Post an offending sample of your data - like Doug I cannot reproduce the > fault on the basis of the information you have provided. [quoted text clipped - 48 lines] > >>>>> -- > >>>>> Kim Change the text file to produce a legitimate time format by using colons instead of decimals. Signature<>>< ><<> ><<> <>>< ><<> <>>< <>><<> Graham Mayor - Word MVP My web site www.gmayor.com Word MVP web site http://word.mvps.org <>>< ><<> ><<> <>>< ><<> <>>< <>><<> > The time field in my text file is formatted like this: > [quoted text clipped - 62 lines] >>>>>>> -- >>>>>>> Kim I have no control over the text file since it's produced by another application. I don't understand why 13.30.00 is interpretted correctly but 08.30.00 isn't. SignatureKim > Change the text file to produce a legitimate time format by using colons > instead of decimals. [quoted text clipped - 65 lines] > >>>>>>> -- > >>>>>>> Kim Kim, I believe your data/values are being read like this: 08.30.00 = August 30, 2000 or just August 30 at midnight or 00:00:00 hrs Because the "08" can represent the month of August 13.30.00 = 13:30:00 Since there is no 13th month, the "13" (or higher figure), will reflect the 24/military time correctly. SignatureAdd MS to your News Reader: news://msnews.microsoft.com Rich/rerat (RRR News) <message rule> <<Previous Text Snipped to Save Bandwidth When Appropriate>> I have no control over the text file since it's produced by another application. I don't understand why 13.30.00 is interpretted correctly but 08.30.00 isn't. SignatureKim |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.