Abstract: A system and method for building and linking an interpretive procedure so as to enable a compiled computer program to invoke the interpretive procedure are described herein. A target object code is modified to include information identifying files associated with the interpretive procedure. A compiled representation of the interpretive procedure is generated by linking together adapter code, the modified target object code, and an interpreter. The compiled representation of the interpretive procedure is invocable by a compiled computer program. The adapter code is in binary and includes an interpreter command module. The interpreter command module when executed causes the interpreter to load and interpretively execute the files associated with the interpretive procedure. The adapter code also includes a parameter conversion module, which converts the parameter list to the interpretive computer language of the interpretive procedure.

Abstract: A system and method for transferring a file from a client platform to a server platform. A procedure.sub.-- to.sub.-- invoke parameter is set equal to information identifying a file transfer procedure located at the server platform. A pointer in a first "sqlvar" parameter is caused to point to the string representing the file, and a pointer in a second sqlvar parameter is caused to point to a file name of the file. The first and second sqlvar parameters are part of an input.sub.-- args parameter. A "sqleproc" function is invoked at the client platform. The procedure.sub.-- to.sub.-- invoke and input.sub.-- args parameters are passed to the sqleproc function. The sqleproc function when executed causes the input.sub.-- args parameter to be passed to the file transfer procedure at the server platform, and also causes the file transfer procedure to be invoked at the server platform.