Hi,
Panorama X Server version: 10.2.0.b39 (4486)
Panorama X Client version: 10.2.2b1 (4568)
Is there a way to review record transactions and retrieve inadvertently deleted ones?
Also, I realize the server has not been updated in a while. Could the version mismatch cause any data loss issues?
TIA,
– Mark
The title of your post says “lost records”, but in the body you say “inadvertently deleted”. Does this mean that some user deleted a record when they should not have? There is no way to recover a record that has been deleted. No one has ever asked for that before, but I suppose that could be a feature request.
As for reviewing transactions, you can enable logging on the server. However, this will not let you review the actual data that was deleted, it will only tell you the ID numbers of the records that were deleted, and when.
Yes, I think 9 months qualifies as “a while”. Be advised that there is NO testing of new clients with older versions of the server. I don’t think that a version mismatch would cause a problem, but I cannot really assure you that I know that there isn’t a problem. Also, there have been a number of fixes in the last 9 months, including to the server. I’d ask if there was a reason the server hasn’t been updated, but I’m pretty sure I know the answer.
I don’t know this acronym. I did a google search but I’m pretty sure you’re not telling me that you’re having a stroke. At least I hope not!
Yes, exactly. (I’ve updated the title. 
)
Yeah. I was afraid of that.
Do you have a recommended backup strategy to mitigate losing data due to inexperienced (or sloppy or …) users or retrieving deleted records? (If it’s in the docs, I’ve obviously missed it.)
The server runs on a remote mac mini server. It “just works” … and I’m hesitant to rock that boat. LOL. (The computer has an uptime of 222 days, 20 hours, 9 minutes. PanoX Server has been running for 182 days, 20 hours, 7 minutes)
Though, if you recommend updating, I’ll add that to the list.
It means: Thanks In Advance! 
– Mark
Not really.
Panorama X already defaults to displaying a warning alert before deleting a record in a shared database. So unless you’ve disabled that (it’s in Preferences) they are already deleting the record and then confirming that they want to delete.
If you wanted to go further, you could add a .DeleteRecord procedure to your database. For example, you could require a password before allowing deletion. Or maybe require them to solve a simple math problem 
If I don’t recommend updating, then what is the purpose of my life and work? 
Ok, that makes sense, and you’re welcome. But I’ve got to tell you, that doesn’t come up even once in the first ten pages of results of a Google search for TIA. It’s all about strokes (Transient Ischemic Attack).
Could be a keystroke>
Look under “TIA texting slang.”
Thanks.
To clarify, I already believed Mark. I figured there was some way to modify the search to find it on Google, but since I already had the answer I didn’t bother.
There is always Time Machine. That would allow you to retrieve an older copy. Then in Panorama Preferences (PanoramaX > Settings) go to the Client tab and Disable Server Connections to open it without it synching.
Open it, find the deleted records then use Copy Record and Paste Record to add it back into the active db.
If you’re really concerned about this being an ongoing problem, you could set .DeleteRecord to save the record to another file, a journal of sorts, i.e. use FileAppend to save deleted records to a text file
Although the horse has left this barn, one thing to be careful about in your backup scheme is to have only one backup edition, especially if it’s automatic.
Sometimes a “problem” isn’t discovered until a day, maybe a week has passed since the actual event. During that time, you automatic backup may have copied the problem over that last good version you had.
When I wrote a routine for the local community college, I knew a variety of students, with differing skills and attitudes, would be entering data. So I my routines kept a backup for each day of the week. Then consolodated that into a Weekly BackUp and that into a Monthly backup.
If there was a problem, I could “Undo” back to a date where everything was good.
Now-a-days, Apple provides TimeMachine technology. I have that running, and I also use SuperDuper to make a periodic copy of the main drive. These days, storage is cheap.
This is a personal choice and maybe related to geezerhood, but I also don’t like the Cloud. I want my data local on my machine. I’m sure Cloud technology is great for a company that is sharing data/projects far and wide. But for my projects, I prefer local - independent of internet access.
Would there be a way of setting up another file where one could transfer the deleted record as a backup, prior to deleting in? That new file would just contain records that one would delete from the main file.
Use .DeleteRecord:
Sorry, James, I missed that in your previous post. As usual, you are on top of things…thank you for all you do for Pan users…(including me).