4C Client/Server Reported Bugs

4C Client/Server Reported Bugs

26 June 2009

25 May 2009

15 October 2008

05 March 2008

07 December 2007

30 November 2007

21 November 2007

30 July 2007

21 March 2007

08 January 2007

11 December 2006

02 June 2006

29 March 2006

28 February 2006

17 January 2006

04 January 2006

01 November 2005

02 April 2003

  1. There is no way to disable implicit linking or execing of 4C programs within a TabFolder. It probably is too complicated to try to implement this kind of control because: This problem can easily be worked around by better application design. Some ideas:

14 September 99

  1. For applications that need system files, you must export the system files and import them every time you install the 4C Server. You MUST not have the debug file definitions in your application directory though.

14 Oct 97

  1. When a 4C utility run from a command line connects to the 4C server, you will need to supply a login name and passwd. If you do not have a passwd, you must type ^D at the passwd prompt.
  2. All Paths and Env Vars need to use the Unix File Separator '/' even on NT Machines. This is especially important for XLTMP.

27 May 97

  1. You cannot change the font of a layout while running.
  2. The NT Server version of 4C Must be loaded on the C: drive Fixed: 10/1/97

20 May 97

  1. When running xled from the 4cclient, the cmd is limited to 120 characters. Since the connect string and the path must be passed in the cmd, a verl long path name will cause xled to fail. You can mostly avoid this by specifying the program directory as the FIRST data directory in your XLDATA var. Fixed: 10/1/97
  2. In order for scimport to work, there MUST be an FCServer entry in the XLCONFIG file that specifies the local machine and it MUST have Local=Yes specified.
  3. scimport, if run from the command line, looks at the XLPROG, XLDATA, and XLEXP vars in the local environment and does not specify an application to the server.
  4. It is possible that the 4CSRVRCONFIG file may still be overwritten. Make sure you save yours.
  5. The Debugger may act wierd when stepping thru sys.link_progs if the linked to prog links back to the link from prog without exiting.

Back to Top