Recent content by jjjt

Makes sense. Thanks Chris.

Chris, Rick, Thanks for the input - COMRETURNERROR() is exactly what I was looking for. With regards to the WinAPI, what are its relative merits in relation to the Scripting Object? I think I am right in saying that if we use the Scripting Object, the user has to have the right version...

Hi, We're using VFP8 and the following code to copy a folder: oFSO = CREATEOBJECT("Scripting.FileSystemObject") oFSO.copyfolder(source, destination,.F.) and it works fine until such time as somebody is editing one of the files contained in the folder, at which point we get a "COM command...

That's our suspicion, too. If we get anything concrete, I'll let you know.

A PACK does reduce the size of the Memo file by a huge amount - we have a reindex and pack utility in our app, and recommend that users run it regularly, but more often than not they seem to ignore the advice. Horses and water and all that... In any event, we know now that a PACK will stop the...

We've been experimenting and getting exactly the same results Griff has seen - carrying out a lot of edits on Memo fields drastically increases the size of the Memo file. Thanks to everybody for their help, we've learnt some stuff about memo fields...

Or does the PACK do both?

The table we are looking at has 171,000 records and there are 13 memo fields per record, though the vast majority of them contain no data. The average size will vary depending on how the user is using the memo fields and can range from a couple of words to a page of notes - I would say that in...

One thought - we never had this problem before we started to use v8 of VFP. Could this be it?

These memo fields only hold text. No pictures or anything like that. This would mean over 1.5GB of "bloat" that would make it increadibly inefficient! Surely it cannot be right?

But how can they be getting to 2GB in the first place? When I did a PACK the Memo File went from over 2GB in size to 326,436KB. I assume that the data stored in the Memo File represents 326,436KB what was the rest taken up with?

We have a problem where at times our users experience an error saying: "There Is Not Enough Disk Space For....." The message ends with the name of a memo file. As it happens there is loads of space for the memo file over 90GB but the memo file itself is just over 2GB. The corresponding table...

We feel the index is correct and the table is wrong. Because browsing with SET DELETED ON does not show these rogue records but browsing with SET DELETED OFF shows them but with no deleted mark on them. We feel the records should be shown with a deleted mark against the record when browsing...

For example: We have a table with 10 records in, 3 are flagged for deletion (the little black mark when browsing a table). However the index reports 4 are deleted (We have an index on DELETED()) and as far as we are concerned this is correct because: 1. It is in line with what our code should...

I have used the code above and it does exactly what I need but it nearly caught me out, so I figured I'd post even though the thread's been dead for a while. I created three tables in my document and gave each a caption, 'Figure 1' to 'Figure 3'. In my text I made cross references to 'Figures...