Just one obvious thing nobody mentioned - maybe because it's obvious:
The best protection against data loss, no matter if by table corruption or the file deletion you encountered, is a backup of data. That should be a feature of your software. You're concentrating very much on just the problem...
Sorry, I got this wrong.
You also said: "In one case, the owner is the only one using our software. There isn't any good reason to sabotage himself."
I took that as there being a single user mode, where you might give the user the ability to modify the tables.
There could also be the case...
Have you even found a bak file? The only documented case for a bak file is using the table designer. And that's not a runtime feature. If you just work on data with either APPEND, REPLACE and (xBase) DELETE or SQL INSERT/UPDATE/DELETE you never get a bak file.
I agree with what ggreen said last. But when your dbf is missing after an alter table or using the table designer to change the structure, that means storing the latered table failed and you may have the old structure in a DBC or have some informations about the table updated, some not. In...
The solution that always works is a reportlisteners OnPreviewClose method and SYS(2040) works with SET REPORTBEHAVIOR 80 or in older VFP versions (up to 8). So there's a solution to any case.
Just watch out, in REPORTBEHAVIOR 90, SYS(2040) does not become "2".
I double checked that in VFP9 9.0.0.7423. I think it's be design, as VFP 9 report behavior is using a pagecage that exactly prints what preview showed and thus does not do a separate pass for actual printing. You might be able...
That's also an option I thought of, but it's following the whol off topic thread. Since Vince said his software is used by one person and they want to use it, I don't see a reason they sabotage it at all and that train of thought was gone far off and too far in the totally wrong direction.
If...
Which version of VFP are you using. If it's the usual VFP9, you can make use of the reportlistener "OnPreviewClose" method. The help on that has good example code.
That's not a good idea, you know a dbf most of the time has a cdx and fpt file, too. You said that one has no fpt, but that's not generally the case, is it? If you restore some state of a dbf that was saved as a .bak file that doesn't match the fpt and cdx files, you gain nothing. Find the root...
This was done without specifing the "from left" value but using the snap-to-grid functionality. For finer granularity in smaller steps I reduced the grid spacing, that's up to you, of course. You also have several other tools others also mentioned already, like the layout toolbar.
You can...
Just to showcase what is possible:
1. The Report Designer screenshot:
2.The Report Preview Screenshot
3. PDF Output viewed at 400% zoom:
I don't see any problem. Do you?
The snap to grid function only works whn using the mouse to position objects, just like it works in the form designer.
That's not true. All left sides of bands are the same offset from the left page margin: The margin width you set, so put in the same "from left" number and the labels left...
Fine, SitesMasstec.
The HPOS values are the "from left" position. I don't see them matching for Emissao and Navio, for example.
So you haven't alligned these labels in the designer. Simple truth, simple effect. Of course you don't get aligned output, it's not even aligned in the design.
Neither SQL (Insert/Update/Delete) nor xBase (Replace, Append, Delete) do that. I wonder what you mean by updating tables.
I already mentioned ALTER TABLE, if you mean structural updates, but they are not the normal operation. And by the way, not even using transactions creates new/other files...
There's Sir Veillance hindering that. And working contracts. Legal stuff.
In short: There's no perfect safety, but there also isn't a perfect crime.
I'm very sure the outcome will either be the DBF is found in quarantine or Vince finds code that deletes the file, unintentionally, of course...
I don't know how good you are at user management, but you can clearly limit company users to not use system components, disable them to install any software or run any software uninstalled, too. The core thing to use is group policies restricting what users can do. I worked for a company only...
That's basically not the problem in a company environment, where users have limited permissions. Using computer management needs admin permissions.
You still have a point. The simple solution to avoid deleting files is not giving that permission to users, which obviously still depends on them...
Can you display the result of this query, please?
Select Cast(Expr as varchar(50)) as caption, hpos, vpos , Cast(fontface as varchar(50)) as font, fontsize, float, stretch From yourreport.frx Where ObjType=5
EinTerreaner - you have to know this. You'd not be stupid to set your share name as environment variable.
You'd need to be able to run process monitor and monitor which files a process accesses. You'd need to be able to write code listing shares. It's not a safe/secure way to protect files to...
A software can use UNC paths and those will not be seen by users, necessarily. So you create a share, name it, but don'T map it, then your software can use files without the user knowing about them.
You're right about that, but that would point out a user would need to have more knowledge about...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.