Mar 21st, 2005, 11:05 AM
A client has requested an e-mail formatted in OTF format. Anybody know what on earth THAT is? A quick glance at microslouch's web site brings up nuthin.
Client claims their client is sending e-mails in this format, yet I can see no link to Outlook Express and OTF anywhere on the net.
Any assistance would be greatly appreciated.
Mar 21st, 2005, 11:35 AM
Make that OFT format - not OTF.
Mar 21st, 2005, 02:44 PM
OFT is Outlook forms template.
(I just did a search, I am not a programmer so please don't ask me anything about OFT.)
To give you some direction, try these links:
Good explanation of forms (http://www.pcmag.com/article2/0,4149,348,00.asp)
Outlook exchange (http://www.outlookexchange.com/articles/home/wisniewski01.asp)
More drivel (http://www.outlookcode.com/d/launchform.htm)
Microsoft drivel (http://support.microsoft.com/kb/146636/EN-US/)
From Microsoft website:
Using Outlook Template (.oft) Files
You can save an Outlook form as an Outlook Template (.oft) file. Users can open the form by opening the .oft file from the file system. You can store the forms on a server and put shortcuts to the form on the users' desktops. Alternatively, you may want to put a shortcut to the folder that contains the form. Because these forms are not published, they are considered "one-off" forms. Using this approach may cause issues if you use Microsoft Visual Basic Scripting Edition (VBScript) code in the forms: • If you use versions of Outlook that have the Security Update features installed (by default, these features are included with Outlook 2002), the code in the form does not run unless an administrator customizes the Outlook security settings on the Exchange computer.
• VBScript code in one-off forms generates a security warning that prompts the user to enable or disable the code in the form, which is typically undesirable.
Because one-off forms behave this way, avoid using .oft files. Publish forms instead.
Mar 21st, 2005, 04:12 PM
I did find a couple of those links, but...
Looks like the client is using an outdated version of Outlook and expects all users to be able to read these files. The OFT file sent to our token PC [used for testing and converting files only] could not read that file in Outlook.
So not sure what the client wants to do with this.