the configuration is pretty simple.

Open the database, go to:
Database settings : Backup : Configure
turn on the check box(es) you want to be backed up and add any 
additional file(s) you want
set your destination, and schedule.

the .4BK file obtains whatever is supposed to be backed up.
The 4BL is a log file, and I assume tells 4D what is supposed to be in 
the 4BK film and how large.

To restore:
Open 4D 
Fiel menu : Restore
Select 4BK to restore, and select a destination
wait

if, as default, structure and data are included you will have a 
functional database, and structure.

As for reading -- the documentation....  RTFM  :)
not that I do .... :)

Chip



On Fri, 9 Nov 2018 10:47:07 -0500, Sandor Szatmari wrote:
> I’m glad to learn that.  However, the way our backups are configured 
> I only see 4BL (the log) and and 4BK (the data) files.  Looks like I 
> need to learn more about the backup configuration process.  What is 
> the recommended way to configure backups so that I would have access 
> to these individual files?  Or, are they accessible individually 
> during the restore process from the 4BK file?  Also, if there is any 
> good reading on this you could point me too, It’d be appreciated.  
> Thanks for your response, very helpful indeed!
> 
> Sandor Szatmari
> 
>> On Nov 9, 2018, at 10:08, Chip Scheide <[email protected]> wrote:
>> 
>> depending on what your form method looks like, it does not hurt (much) 
>> to simply turn everything on.
>> Chip
>>> On Fri, 9 Nov 2018 09:24:16 -0500, Sandor Szatmari via 4D_Tech wrote:
>>> OK, so it looks like there's some strange bug I ran into.  For some 
>>> reason most of the events for my forms got disabled at the form 
>>> level.  So, even though they were checked off at the element level 
>>> the form was not registered for those events anymore.  I am going to 
>>> have to go through all the UI elements and look though their event 
>>> handling code to make sure all the correct events are registered at 
>>> the form level.
>>> 
>>> 
>>> Has anyone heard of this before?  If anyone knows of a way to best 
>>> determine the previous state of the form event configuration any 
>>> thoughts would be appreciated.
>>> 
>>> Thanks,
>>> Sandor Szatmari
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> Senior Software Developer
>>> Bristol Capital Inc. - InfoPlus
>>> 201 746 7215
>>> www.infoplusonline.com
>>> 
>>> 
>>> 
>>> From:   Sandor Szatmari via 4D_Tech <[email protected]> 
>>> To:   <[email protected]> 
>>> Cc:   Sandor Szatmari <[email protected]> 
>>> Sent:   11/9/2018 12:18 AM 
>>> Subject:   Forms Stop Receiving Certain Events 
>>> 
>>> Has this ever happened to anyone?  UI Elements on certain forms 
>>> appear to have stopped receiving certain events.  This form and 
>>> related code that have been functioning for many many years.  I was 
>>> adding an additional page to the form when this started happening.  I 
>>> did not edit or change the code or properties on any of the other 
>>> pages/ui elements.  Any help in tracking down the cause would be 
>>> helpful and greatly appreciated.  I do have backups but I don't want 
>>> to roll back the database because it is an active database where data 
>>> is added every day.  I am under the impression that you cannot roll 
>>> back the interface programming separately from the actual data.  An 
>>> example is below.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> Platform: MacOSX (10.11.6)
>>> 4D Version: v15 R5
>>> 
>>> 
>>> Here's an example…
>>> 
>>> 
>>> A Popup button, has 'On Load', 'On Clicked' and 'On Unload' enabled 
>>> in the property list (i.e. checked off').
>>> 
>>> 
>>> The object method for the popup has a case statement for reacting to 
>>> these events. (The rest of the code is removed for brevity)
>>> 
>>> 
>>> 
>>> 
>>> $TheEvent:=Form event 
>>> Case of  
>>> : ($TheEvent=On Load) 
>>> 
>>>                 ALERT("Load") 
>>> : ($TheEvent=On Clicked) 
>>>               ALERT("Clicked")  
>>> : ($TheEvent=On Unload) 
>>>               ALERT("Unload")  
>>> End case 
>>> 
>>> 
>>> The only alert that is displayed is the unload alert.  
>>> 
>>> 
>>> How can I figure out where this the events are being lost/swallowed.
>>> 
>>> 
>>> Thanks in advance,
>>> Sandor Szatmari
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> Senior Software Developer
>>> Bristol Capital Inc. - InfoPlus
>>> 201 746 7215
>>> www.infoplusonline.com
>>> 
>>> CONFIDENTIALITY NOTICE: This email (and any related attachments) 
>>> contains information from InfoPlus (a service of Bristol Capital, 
>>> Inc.). It is intended only for the addressee and may contain 
>>> information that is confidential and/or otherwise exempt from 
>>> disclosure under applicable law. If you are not the intended 
>>> recipient or are acting as agent for the intended recipient, any use 
>>> or disclosure of this communication is prohibited. If you have 
>>> received this communication in error, please notify us immediately to 
>>> arrange for the appropriate method of returning or disposing of the 
>>> communication. If our respective Companies have confidentiality 
>>> provisions in effect, this email and the materials contained herein 
>>> are deemed CONFIDENTIAL and should be treated accordingly unless 
>>> expressly provided otherwise.
>>> **********************************************************************
>>> 4D Internet Users Group (4D iNUG)
>>> Archive:  http://lists.4d.com/archives.html
>>> Options: https://lists.4d.com/mailman/options/4d_tech
>>> Unsub:  mailto:[email protected]
>>> **********************************************************************
>>> 
>>> CONFIDENTIALITY NOTICE: This email (and any related attachments) 
>>> contains information from InfoPlus (a service of Bristol Capital, 
>>> Inc.). It is intended only for the addressee and may contain 
>>> information that is confidential and/or otherwise exempt from 
>>> disclosure under applicable law. If you are not the intended 
>>> recipient or are acting as agent for the intended recipient, any use 
>>> or disclosure of this communication is prohibited. If you have 
>>> received this communication in error, please notify us immediately to 
>>> arrange for the appropriate method of returning or disposing of the 
>>> communication. If our respective Companies have confidentiality 
>>> provisions in effect, this email and the materials contained herein 
>>> are deemed CONFIDENTIAL and should be treated accordingly unless 
>>> expressly provided otherwise.
>>> **********************************************************************
>>> 4D Internet Users Group (4D iNUG)
>>> Archive:  http://lists.4d.com/archives.html
>>> Options: https://lists.4d.com/mailman/options/4d_tech
>>> Unsub:  mailto:[email protected]
>>> **********************************************************************
>> ---------------
>> Gas is for washing parts
>> Alcohol is for drinkin'
>> Nitromethane is for racing 
> 
> 
> 
> CONFIDENTIALITY NOTICE: This email (and any related attachments) 
> contains information from InfoPlus (a service of Bristol Capital, 
> Inc.). It is intended only for the addressee and may contain 
> information that is confidential and/or otherwise exempt from 
> disclosure under applicable law. If you are not the intended 
> recipient or are acting as agent for the intended recipient, any use 
> or disclosure of this communication is prohibited. If you have 
> received this communication in error, please notify us immediately to 
> arrange for the appropriate method of returning or disposing of the 
> communication. If our respective Companies have confidentiality 
> provisions in effect, this email and the materials contained herein 
> are deemed CONFIDENTIAL and should be treated accordingly unless 
> expressly provided otherwise.
> 
> 
---------------
Gas is for washing parts
Alcohol is for drinkin'
Nitromethane is for racing 
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to