Re: Field Data to Microsoft Word.

Dan,
You are correct in your thinking about just blaming Microsoft but I know
what is going to happen. My users are going to want a fix. I will have to
change the code and write the data to an Excel file and then to word. I
think that is what Microsoft wants, get rid of VFP and use access!!!. As far
as I can tell you can't use mailmerge to a VFP table and now you can't use a
csv file without the warning, unless you modify the register, so now you
have to go to Excel but if the code was in access it would be OK. Sounds
fishy to me, it stinks.
TonySper

"Dan Freeman" <spam@xxxxxxxxxxxxx> wrote in message
news:OwqzDCijJHA.4644@xxxxxxxxxxxxxxxxxxxxxxx
What's so terrible about it?

You either use the registry classes found in the FFC to create that key
yourself or provide a .REG file to your users.

I'd lean to the latter because it gives the users the choice. Explain to
them that Microsoft screwed the pooch and they can either double click
this .reg file once or live with the dialog.

<shrug>

Dan

TonySper wrote:
Dan,
Yes they did reply but the fix is terrible. Microsoft says that they
put this warning in XP SP3 as there was a security risk that they
blocked. The fix is to go into the register and add modify the
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Word\Options
"SQLSecurityCheck"=dword:00000000
This means that all the people that have been using my existing
applications and have installed SP3 now have to modify their
registers. That is just not going to happen. This is terrible.
This can be found at http://support.microsoft.com/kb/825765
TonySper

"Dan Freeman" <spam@xxxxxxxxxxxxx> wrote in message
news:OOLQTFhjJHA.4372@xxxxxxxxxxxxxxxxxxxxxxx
There is a way to do it, but you might want to ask the Word experts.
:-) Try microsoft.public.word.docmanagement


I've seen this asked and answered over there.



TonySper wrote:
Thank you and you are correct. I just thought that somewhere out
there that someone may have done it. I have tried writing it to a
.csv file and then putting it into fields in word but it still pops
up with that warning about sql entering the fields. There must be a
way of stopping that message or maybe I can use automation to answer
it yes. Will do more research. Thanks again for the reply.
TonySper

"Mark Burgum" <Markb@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:uyrjFJbjJHA.6124@xxxxxxxxxxxxxxxxxxxxxxx
no,

its part of a commercial package produced by the firm i work for. i
dont think that would be ethical.

i know we used http://www.hentzenwerke.com/catalog/autofox.htm

as a reference when we developed this part of the package. another
thing that helps is to look at the word object using the object
browser in foxpro. i found that usefull when automating Excel,
unfortunatly i have not done much word automation.




"TonySper" <tsperduti@xxxxxxxxxxxxxxxxxxx> wrote in message
news:u3hCN5TjJHA.5588@xxxxxxxxxxxxxxxxxxxxxxx
Can you send me a copy of the code???
Tony

"Mark Burgum" <Markb@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:uuJZQMTjJHA.4276@xxxxxxxxxxxxxxxxxxxxxxx
it looks like we are adding the mailmerge fields to the word
document via automation

oDocument.MailMerge.Fields.Add( oBMRange , "CONTACT")



and then performing the merge



oDocument.MailMerge.Execute()



its not my code, but from conversations i have overheard that is
how we are doing it.



"TonySper" <tsperduti@xxxxxxxxxxxxxxxxxxx> wrote in message
news:eEgkI9SjJHA.504@xxxxxxxxxxxxxxxxxxxxxxx
I was looking at that but then I think you have to create the
mailmerge in word to use the excel. Did you use the mailmerge in
word or VFP?? TonySper

"Mark Burgum" <Markb@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23CEgQjOjJHA.5724@xxxxxxxxxxxxxxxxxxxxxxx
we added a similar feature to our package. we ended up
exporting the data to excel and merging from excel, I think we
did it that way to avoid that prompt as well as the need to
have the odbc drivers for foxpro, but haven't tested it in a
while. "TonySper" <tsperduti@xxxxxxxxxxxxxxxxxxx> wrote in message
news:%23H1OCxKjJHA.4028@xxxxxxxxxxxxxxxxxxxxxxx
If I use the wizard to create the Word mailmerge file and each
time I run the doc file I get a warning "Opening this document
will run the following SQL commands" and I have 2 options. YES
NO. I can not put this into an application that a user runs
and have that warning pop up. Is there another way to set up
a doc file with fields that I can call from VFP8 and open up
and print the doc file without the warnings??
TonySper

"TonySper" <tsperduti@xxxxxxxxxxxxxxxxxxx> wrote in message
news:ut2BdxIjJHA.5124@xxxxxxxxxxxxxxxxxxxxxxx
Yes, Thank you. But how do you automate running VFP to enter
the fields from the database into the mailmerge. That is the
question. TonySper

"Usenet" <Mark@xxxxxxxxxxxxxxxxxxx> wrote in message
news:VA.0000001f.0039798f@xxxxxxxxxxxxxxxxxxxxxx
In article <OsxQzbFjJHA.5732@xxxxxxxxxxxxxxxxxxxx>, TonySper
wrote:
I would like to call up a Microsoft Word file that is pre
written and have
fields from my data base entered into areas of the
application.

What you want is a mailmerge document, shirley?

Mark




.

Relevant Pages

  • Re: Field Data to Microsoft Word.
    ... TonySper ... It's a good fix. ... Excel file and then to word. ... csv file without the warning, unless you modify the register, so ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Field Data to Microsoft Word.
    ... TonySper ... It's a good fix. ... the warning, unless you modify the register, so now you have to go ... to Excel but if the code was in access it would be OK. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Field Data to Microsoft Word.
    ... TonySper ... It's a good fix. ... the warning, unless you modify the register, so now you have to go ... to Excel but if the code was in access it would be OK. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Field Data to Microsoft Word.
    ... oh i think we can all understand that, microsoft has the good manners of a ... TonySper ... VFP table and now you can't use a csv file without the warning, ... so now you have to go to Excel but if ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Benefits of upgrading to Excel2003
    ... You probably don't have access to Excel 2002 and excel 2003 so I've ... Key new features in Microsoft Excel ... Web queries to Extensible Markup Language files. ... If you are not using the specific language version of Microsoft Office ...
    (microsoft.public.excel.misc)
Loading