There is an ioctl command for that GETFILENAME
From: jbase@googlegroups.com [mailto:jbase@googlegroups.com] On Behalf Of Rick
Weiser
Sent: Thursday, April 13, 2017 10:45 AM
To: jBASE
Subject: Back doing some jBASE work
Hi Guys,
So, I am back doing some jBase work
They truly aren’t necessary as there are certainly better ways to manage the
environment. Question: is this going to reside on a Windows PC, a Windows
Server, a Unix box, etc. How many people will need access and how are you
planning on giving them that access? As I said, your particular
Best practices are best defined based upon your particular needs. The first
part (purely using examples) is to separate the environment from the
application(s) For example, load the server with c:\jbase5\5.
Load the application(s) on
Remember, it is still 32 bit limited, even though it will run on a 64 bit
machine. File and index sizes limits are still the same.
From: jbase@googlegroups.com [mailto:jbase@googlegroups.com] On Behalf Of
Richard Kann
Sent: Thursday, February 25, 2016 2:08 PM
To: jbase@googlegroups.com
Remember, you can use 32 bit applications on a 64 bit OS but not the other way
around. You can go to the 64 bit version of your new OS.
From: jbase@googlegroups.com [mailto:jbase@googlegroups.com] On Behalf Of Mark
Hogden
Sent: Friday, March 14, 2014 12:51 PM
To: jbase@googlegroups.com
Implement triggers on sensitive files. Regardless of how a record is changed
(jed, edit, program, etc.), the trigger allows capture of who, what, when, etc.
From: jbase@googlegroups.com [mailto:jbase@googlegroups.com] On Behalf Of
fakhruddin siddique
Sent: Friday, October 25, 2013 1:55 AM
To:
Depending upon your file by file requirements, 1 trigger file in a pre-write
position might serve for all. Of course, again depending upon what you want to
do, it might be the same amount of work to a) handle the failed write (null
key) as b) handling the null key BEFORE you write. If a
Look UP IOCTL(handle,JIOCTL_COMMAND_SEQ_CHANGE_RECORDSIZE, 2560) which
would set the buffer to 2560 bytes for opened filehandle handle. The
default is 1024 bytes but can be set by IOCTL (include JBC.h)
-Original Message-
From: jbase@googlegroups.com [mailto:jb...@googlegroups.com] On
Consider using only the month not both month and year. The part files
can be precreated with no problem. If after a few years, the parts
approach 2Gb, then either create an archive and prune the older records
into it or otherwise preserve/dispose of them.
-Original Message-
From:
Actually, Gentlemen, the documentation is on page 60 of the programmer's
guide. The function is called CALLONEXIT
From: jBASE@googlegroups.com [mailto:jb...@googlegroups.com] On Behalf
Of Jim Idle
Sent: Tuesday, May 12, 2009 10:02 AM
To: jBASE@googlegroups.com
Subject: Re: ON EXIT
Daniel
be called as the processed terminated.
From: jBASE@googlegroups.com [mailto:jb...@googlegroups.com] On Behalf
Of Jim Idle
Sent: Monday, May 11, 2009 12:16 PM
To: jBASE@googlegroups.com
Subject: Re: ON EXIT
David McGehee wrote:
I seem to remember reading that jBase had an ON EXIT function
. I recreated the problem file and the TRANSEND
problem went away.
-Original Message-
From: jBASE@googlegroups.com [mailto:jb...@googlegroups.com] On Behalf
Of Jim Idle
Sent: Thursday, April 30, 2009 10:43 AM
To: jBASE@googlegroups.com
Subject: Re: Transaction Boundaries Problem
David
Windows Server 2003 environment with 4.1.5 JBC question: Using a
filedata = DIR(filepath_and_name) gives me the correct size and type of
object. Hovever, the date and time seem to be for a Timezone other
than my @TIMEZONE. It looks like GMT0 but that is a timezone which
does not use daylight
Microsoft Server2003 jbase 4.1 environment. We need a different method
of making http: connections from jBase. We are currently using a CALLC
custom-written interface for which we no longer have the code.
--~--~-~--~~~---~--~~
Please read the posting guidelines
14 matches
Mail list logo