If you are keeping the form open for a long time is it possible that when you 
close and re-open it there just happen to be a large number of $$$ files and 
R:Base has to create a filename based on something - I have no idea what - so 
could it by chance just happen to be starting a new sequence with the same name 
again?

If that sort of thing is happening then you might test it by closing the form 
more often and/or the database as well.
R:Base is now very good at tidying up the left over $$$ files but, AFAIK, only 
when you close it.
You might also check, if you haven't already, that the users really can delete 
the $$$ files...

Regards,
Alastair.


  From: Kenny Camp 
  Sent: Thursday, April 22, 2010 4:04 PM
  To: RBASE-L Mailing List 
  Subject: [RBASE-L] - RE: Need help on (filename(0)) and Scratch settings - 
RBase 7.6.8.3031 for Windows full and compiled versions.


  Thanks Javier,

   

  Your approach is much like I used to do, and will probably return to, and 
your results of different filenames is what I normally experience.  

   

  Something seems to go wacky after a while during  a long session. 

   

  I'm currently going through all the changes I have made over that last 
several months, looking for clues.  

   

  The main form everyone uses is very complex and I keep adding features.  They 
stay in this one form (loading other forms, reports, and routines  from it) all 
day long, even though I recommend closing the session when they go to lunch or 
break.  

   

  I probably need to simplify this form. Break it up into several separate 
forms. This would reduce the memory needed for variables and objects.

   

  Kenny

   

   

   

  From: [email protected] [mailto:[email protected]] On Behalf Of Javier 
Valencia
  Sent: Wednesday, April 21, 2010 9:02 PM
  To: RBASE-L Mailing List
  Subject: [RBASE-L] - RE: Need help on (filename(0)) and Scratch settings - 
RBase 7.6.8.3031 for Windows full and compiled versions.

   

  Kenny,

   

  This is the command I use to set my scratch file:

   

  CLEAR VAR vChkFile

  SET VAR vChkFile INTEGER = NULL

  SET VAR vChkFile = (CHKFILE('C:\TEMP'))

  IF vChkFile <> 1 THEN

      MD C:\TEMP

  ENDIF

  SET SCRATCH C:\TEMP

   

  I wrote a little snippet to test the filename(0) function as follows:

   

  -- Code to test FILENAME(0)

  SET VAR vFile = (FILENAME(0))

  WRITE .vFile

  SET VAR vFile = (FILENAME(0))

  WRITE .vFile

  SET VAR vFile = (FILENAME(0))

  WRITE .vFile

  SET VAR vFile = (FILENAME(0))

  WRITE .vFile

  SET VAR vFile = (FILENAME(0))

  WRITE .vFile

  RETURN

   

  When Irun the code from the R> prompt, I get the following results:

   

  R>run x.rmd

  C:\TEMP\4bcfaace.$$$

  C:\TEMP\4bcfaacf.$$$

  C:\TEMP\4bcfaad0.$$$

  C:\TEMP\4bcfaad1.$$$

  C:\TEMP\4bcfaad2.$$$

   

  R>run x.rmd

  C:\TEMP\4bcfaad6.$$$

  C:\TEMP\4bcfaad7.$$$

  C:\TEMP\4bcfaad8.$$$

  C:\TEMP\4bcfaad9.$$$

  C:\TEMP\4bcfaada.$$$

   

  R>run x.rmd

  C:\TEMP\4bcfaadb.$$$

  C:\TEMP\4bcfaadc.$$$

  C:\TEMP\4bcfaadd.$$$

  C:\TEMP\4bcfaade.$$$

  C:\TEMP\4bcfaadf.$$$

   

  R>run x.rmd

  C:\TEMP\4bcfaae4.$$$

  C:\TEMP\4bcfaae5.$$$

  C:\TEMP\4bcfaae6.$$$

  C:\TEMP\4bcfaae7.$$$

  C:\TEMP\4bcfaae8.$$$

   

  Which is the expected behavior. Is this where you are getting repeated 
filenames?

  Also, if you are using the generated names and you have a path with long 
names and/or spaces, you definitely need to enclose the expression in quotes. 
You might try setting the scratch setting to something simple such as C:\TEMP 
and see if that helps. BTW, I am on 7.5.

   

  Javier,

   

  Javier Valencia, PE

  913-829-0888 Office

  913-915-3137 Cell

  913-649-2904 Fax

  [email protected]

   


------------------------------------------------------------------------------

  From: [email protected] [mailto:[email protected]] On Behalf Of Kenny Camp
  Sent: Wednesday, April 21, 2010 5:25 PM
  To: RBASE-L Mailing List
  Subject: [RBASE-L] - Need help on (filename(0)) and Scratch settings - RBase 
7.6.8.3031 for Windows full and compiled versions.

   

  Hello List, I thought I had a pretty good understanding of temp files and 
scratch settings but.

   

  Recently,  my programs have started having more and more failures to create 
temporary files in several situations for multiple users.  

  Scratch files are always set to tmp unless I change it during 
troubleshooting.  I created a button to capture scratch setting to verify 
location.

   

  The problem does not start immediately after a new session, reports and 
(filename(0)) work as expected as first.  

   

  But after a while, (1st issue) printing a very simple report to the screen 
with no breaks or eeps results in an error 
C:\docume~1\kenny\locals~1\temp\4bcf107f.$$$ not found!  This error is 
displayed twice even though the report looks OK.  These messages are displayed 
because I have the error messages set ON in order to report if no data found 
(2059) (error variable stays at 0 even when no data).  I checked the scratch 
directory above and there were $$$ files in the scratch directory but not the 
one reported in the error. 

   

  Once this happened, (2nd issue) I tried running a different style of report 
that captures a select statement or tally to a text file.  I test for the 
existence of the result of set v vfname text = (filename(0)) and if it does not 
exist, pause for 1, then try again.  The loop failed the 5 times it loops, 
aborted.  Each failure was the same file name exactly.  I thought the filename 
is created by/affected by the time (seconds?) but I waited over an hour (same 
session) and it is still failing to create this same exact file name.

   

  Is there a way to seed this process (filename(0)) with a new filename so my 
users do not have to close and start a new session? 

   

  I changed my scratch setting to c:\  and it still reported 
C:\docume~1\kenny\locals~1\temp\4bcf107f.$$$ not found! Same file, same 
location.

   

  Any Ideas what I have done to cause this or what is happening?

   

  Confused in OKC,

   

  Kenny



------------------------------------------------------------------------------



  No virus found in this incoming message.
  Checked by AVG - www.avg.com 
  Version: 9.0.814 / Virus Database: 271.1.1/2828 - Release Date: 04/22/10 
07:31:00

Reply via email to