Found 21 records for the .FRM file extension name
There are 20 other file types using the FRM file extension:
.frm - Fractint formula file
.frm - Frame Stacks file
.frm - Megalux Frame image format
.frm - XFDL XML-based language file
.frm - Order or registration form
.frm - dBASE IV report file
.frm - Microsoft Visual Basic form
.frm - WordPerfect document merge form
.frm - MySQL database data file
.frm - CT Summation iBlaze database form file
.frm - DataCAD symbol report file
.frm - EZ-Forms master form
.frm - Fractint formula file
.frm - FrameBuilder document file
.frm - Adobe FrameMaker document
.frm - MYOB form file
.frm - Oracle executable form
.frm - Phoenix visual designer form
.frm - Pro/ENGINEER file
.frm - PhotoFrame picture image
file extension FRM - Universal Forms Description Language
File extension FRM description:
UFDL (Universal Forms Description Language) is an alternate
syntactical representation of XFDL (vnd.xfdl).
UFDL was designed to represent complex business forms on the Web. UFDL
includes support for multiple overlapping digital signatures, and
auditable transaction records. We believe that UFDL can provide full
non-repudiation of contractual forms.
Protecting the privacy of a UFDL document during transmission is done
using common http encryption techniques. Some thought has been given
to providing a built-in system of encryption to protect the privacy of
UFDL documents while they reside in a file system, but no such system
exists at this time.
While UFDL uses a syntax that is reminiscent of a traditional
programming language, the logic natively available from UFDL document
can not be used to alter the data on a users computer or extract data
from that users computer without the users explicit participation.
It should be noted, that mechanisms exist within UFDL to extend the
UFDL language using native code. It is possible to write native code
extensions to UFDL that can manipulate a users local data. (This
mechanism is very much like the "plug-in" mechanisms that are popular
among browsers.) Because of this, any UFDL extension created using
native code need to be explicitly installed by the user on his/her
local machine using the same process as the user would use to install
a new application. UFDL does not provide any mechanism to transport or
install native code extensions from a UFDL document.
UFDL also contains a mechanism for extending its logic through the use
of Java code. Java code extensions can be either installed by the user
using a traditional application installation process or they can be
encapsulated in the UFDL document. When a Java extension is
encapsulated within a UFDL document, it is executed within a Java
sandbox to prevent security concerns.
Mime: application/vnd.ufdl