Search results for query: *

I single stepped this just in my mind. And I showed this, yes. So at least we agree on that. If there is a difference between an expression you set to something, like the IIF expressions often used for grid column dynamicbackcolor, then you put the whole expression into quotes, you set...

Koen, in the first place: Your data sorting shows it works, and I assume that's because you have a modified version of what you posted. Where is the R missing, simply in the function name: HIERACHY (wrong spelling) vs calling HIERA[highlight #FCE94F]R[/highlight]CHY("parenteelid"). It's...

multiple warnings occured performing...." Well, I think this just means the CDX was so unusable at that stage, that just changing the expression in the table designer didn't help. What it would do in detail is dropping the tag as it was and creating it with the new expression. But if you just...

Again, hierarchy("parenteelid") is wrong, it can't do it's job, it isn't passing in the parenteelid value but always the constant string literal "parenteelid". Here are essential points in Griffs function and what "parenteelid" leads to: ? hierarchy("parenteelid") Function HIERARCHY()...

If this was still at the time you called HIERARCHY(" parenteelid") I think we clarified that's not the way to call it, both me and Griff. You have to delete that tag and create it new with the right expression HIERARCHY(parenteelid). You can't just change the expression when the CDX is corrupt...

If your DBF is part of a DBC, it would be a good idea to add Griff's function to the stored procedures. Though when that DBC is in some share then the first call to it would load the DBCs stored procs first and so a local drive location or embedded within the EXE will always be the simplest...

Let me assume what error you get while indexing, it#s the function not being found or array not defined. Maybe it's even just that paranteelid is not the string datatype it should be. Anyway, the function HIERARCHY() must be available, visible, known where to find by VFP, while you index and...

Well, what error do you get? It can't be right just because it doesn't error. Griffs function pulls out the digits separated by points and recombines them the way it's necessary. If you pass in "parenteelid", then there are neither points nor digits in that, you always get an empty string as...

Well, likely there already is a names.cdx as you would always have at least an index on the primary key of a table. But that's just a side note. Otherwise I second Griffs way of indexing, make your index a tag of the normal structural CDX index file a DBF already has anyway. Index usage then...

Besides, just by the way, if you use an IDX instead, the command to do so then is SET ORDER TO IDXFilename, instead of SET ORDER TO tagname, if you make it a tag of the CDX. And I still recommend that, there is no size reason and you CAN and just NEED to make that a habit or start default...

When you name your index PArenteeindex, you don't SET ORDER TO HIERARCHY. It's not that complicated, just distinguish between function and index name and index file name, too. And I always recommend not to name one like the other to get aware of the difference, ie also not to name an index on...

Griffs, procedure still just computes one hierarchy value, not an index. You had to have something like INDEX ON HIERARCHY(keyfield) TAG tagname And for this index to work, the Hierarchy function has to be visible. And I know, that doesn't explain an error message telling you to close a cdx...

You rarely create a CDX, you create a tag in the main CDX of a table, you create this main CDX when you issue the first INDEX ON expression TAG tagname for a DBF or create the first index in the table designer. And the only thing that's special about using a function in an index expression is...

A Software would either have a report embedded in the EXE and so modifying a report doesn't change anything. On the other hand it is possible to have a report extern and use that. When you have that you can of course modify it, but rather would need to keep the unmodified version with a name...

To some more practical advice about how buffering is in general not bad for having control about what is saved to the DBF. You hinted on closing DBFs also to ensure even caches are written. On one side you never have full control over what the OS and hardware do with their caching on top of...

First of all I don't think you can make definite conclusions after one day of changes. Even though, congratulations on getting use to instantaneous on that table, but, well, you could just have been lucky. Ine thing is okay though, we have discussed and confirmed that, keeping tables open means...

One idea that I got while going for a walk: Did you compare USE with any other file opening, especially FOPEN in read mode and for comparison also with read-write mode? Any file, not a DBF, in the same share. Just to see what portion is spent on network connection, permission checks, and getting...

Okay, I bet COVERAGE will be more precise, but nonetheless, I also see you USE IN 0, so we are talking about the opening step. Perhaps TABLEVALIDATE 2 is not the best option as it is not just about a check when opening or closing. Try what you gain by actually turning it completely off and SET...

It's okay, Griff, everyone saw me overlooking things, too. I also understand when a problem causes panic mode, but you see it just takes one or two lines in code to have some more log information and that helps both with a healthy and with a problematic application, no matter if the problem...

Which actually is what this does: https://docs.microsoft.com/en-US/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3 really is comprehensive about what helps in what situation, when you know its oplocks. But I've also seen it so often the discussion just...