Mike,
Is the portion of the app that uses these tables small enough that
you could do some kind of logging routine? You could do an entry
to the log for each function...
Log.cmd
-------------
-- vOper (what's going to/did happen) and vTab (subject table)
-- should be set in calling cmd file
-- run before/after each insert/update/delete
output Log.txt append
wri .vOper
sel count(sys_tableid) +
into vct from sys_tables +
whe sys_table name = .vTab and +
sys_table_type = 'Table'
If vct = 0 Then
sel count(sys_tableid) +
into vct from sys_tables +
whe sys_table name = .vTab and +
sys_table_type = 'View'
If vct > 0 Then
wri .vTab 'is now a view'
else
wri .vTab 'is still a table'
endif
else
wri vTab 'is still a table'
endif
output screen
return
None of the above is tested btw.
If run before and after each insert/delete/update on those tables in
question you might zero in on a pattern.... more info like a datetime
stamp or something that helps you identify what caused the log
could be good.
Ben Petersen
On 8 Jul 2002, at 19:59, mjs wrote:
> Well.........that's a wonderfully nice offer.....but it doesn't happen all
> the time. I can capture the database after the fact, but I can't tell when
> it's happening, until my app tries to use the table, and it ain't there! I
> could just turn all these tables into temporary tables, and recreate them as
> needed....but I wanted to know if I have stumbled onto some kind of
> bug.....it sure it not a feature!!!
>
> Mike
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Tom Grimshaw
> Sent: Tuesday, July 09, 2002 10:20 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Top ten reasons...
>
>
> G'day Mike,
>
> I have 19 tables that I use for the same sort of function you describe -
> the major difference is that mine only store data for the current process,
> none hold it for the whole day. None has ever been deleted or changed to
> a view on me.
>
> Which makes me wonder, is there a cleanup routine run at days end that
> could be being called earlier?
>
> I think it is more likely to be an R:BASE versus the environment problem
> so you are most likely to get the fastest resolution by stripping data
> from your database and sending it to RBTI with explicit instructions on
> how to duplicate it, but if you want to post me your code I will go over
> it for you.
>
> At 16:09 08/07/02 -0400, you wrote:
> >Ok wizards....one of my tables (called archdet2) disapperared.
> >
> >Any ideas?
>
> Warmest regards,
>
>
> Tom Grimshaw
> coy: Just For You Software
> tel: 612 9552 3311
> fax: 612 9566 2164
> mobile: 0414 675 903
>
> post: PO Box 470 Glebe NSW 2037 Australia
> street: 3/66 Wentworth Park Rd Glebe NSW 2037
>
> email: [EMAIL PROTECTED]
> web: www.just4usoftware.com.au
>
> "... the control of impulse -- is the first principle of civilization."--
> Will Durant,
> Pulitzer Prize winning philosopher, writer and historian
>
> the most needed product in the world can be found at
> www.thewaytohappiness.org
>
> This email and any files transmitted with it are confidential to the
> intended recipient and may be privileged. If you have received this email
> inadvertently or you are not the intended recipient, you may not
> disseminate, distribute, copy or in any way rely on it. Further, you should
> notify the sender immediately and delete the email from your computer.
> Whilst we have taken precautions to alert us to the presence of computer
> viruses, we cannot guarantee that this email and any files transmitted with
> it are free from such viruses.
>
> ================================================
> TO SEE MESSAGE POSTING GUIDELINES:
> Send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: INTRO rbase-l
> ================================================
> TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: UNSUBSCRIBE rbase-l
> ================================================
> TO SEARCH ARCHIVES:
> http://www.mail-archive.com/rbase-l%40sonetmail.com/
>
> ================================================
> TO SEE MESSAGE POSTING GUIDELINES:
> Send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: INTRO rbase-l
> ================================================
> TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: UNSUBSCRIBE rbase-l
> ================================================
> TO SEARCH ARCHIVES:
> http://www.mail-archive.com/rbase-l%40sonetmail.com/
>
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/
