Re: Excel issues
Re: Excel issues
- Subject: Re: Excel issues
- From: Oakley Masten <email@hidden>
- Date: Thu, 11 Sep 2008 14:54:45 -0700 (PDT)
Yes, I have found the same thing when comparing the before and after versions. So I too am thinking that it is a header issue. Just don't know how to check that.
The scripting solution will certainly work.
Still annoying to have to do it.
Thanks
Oakley
----- Original Message ----
From: David Wolfe <email@hidden>
To: Olof Hellman <email@hidden>
Cc: Oakley Masten <email@hidden>; Users Group AppleScript <email@hidden>
Sent: Thursday, September 11, 2008 4:20:22 PM
Subject:
Re: Excel issues
In our case, if we open the pre-Excel version and compare it with the post-Excel version in TextEdit, there is no visible difference. Is it possible the difference is in some file header information?
Anyway, your solution should work for an Applescript workflow, which should help both of us.
Thanks,
David
On Sep 11, 2008, at 5:13 PM, Olof Hellman wrote:
My first instinct is to ask what the difference is between the files before and after resaving with Excel.
My second instinct is to suggest that you insert this
tell app “Microsoft Excel”
open <the file in question>
save document 1 with replacing
end tell
into the workflow.
- Olof Hellman
Microsoft MacBU
Not a solution and, again, not Applescript related, but maybe the information will help someone point you in the right direction.
We have a very similar problem with inData imports of tab-delimited text files into InDesign. inData will not recognize and import the files unless they are first opened and saved in Excel.
On Sep 11, 2008, at 12:17 PM, Oakley Masten wrote:
I know this is not the right place to ask but I am hoping someone can direct me to that place.
We are using AppleScripts to run lots of processes and have run into a
glitch.
It is not stopping the process but is just annoying.
We have a sql database on a Windows 2003 server [ I don't know the versions but can find out if it would help] that creates a report for these processes.
This report is an Excel doc.
[side bar - this file does not have a "file type" or a "creator type" in it.
Adding the "file type" and "creator type" via AppleScript does not fix the problem.]
the
report gets imported into a FileMaker 9 database which is used to drive several scripted processes.
The FileMaker dBase will not import the Excel data unless it is first opened in Excel, on my Mac running OSX 10.4.11, and then re-saved. [Opening and saving the file using a Windows machine does not fix the problem.]
Then it imports just fine.
An obvious answer might be to use ODBC you say.
I have already said this and was informed that the Mac side would not be allowed to directly interface with the "real computers" on the dark side. I jest, but that was the response with some liberal translation added.
Has anyone had similar issues and if so where do I look to fix this?
Thanks in advance for any insight here
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden