Peter and Chip,
Thank you both for the constructive feedback on the possibilities.
As the cause of the issue and the consequent resolution (if indeed possible) is
one black-box, I have decided to go back to the most recent stable version and
re-do the necessary changes.
Regards,
Ronnie
My first thought would be damage to the file from the hardware (bad block(s) on
the disk,
but I do not know your situation there
Another thought would be a crash/power outage/etc that occurred while 4D was
writing the structure to disk,
Or before the cache (4D’s structure, or disk) was flushed
On Thu, Dec 3, 2020 at 4:59 PM Tarawerkz via 4D_Tech
<4d_tech@lists.4d.com> wrote:
>
> Thanks Chip,
>
> I’ll try that, hopefully can find a version from not too far back.
>
> Any idea what could have caused this?
My info is not very recent, but few years ago I analysed structure of
data and
Thanks Chip,
I’ll try that, hopefully can find a version from not too far back.
Any idea what could have caused this?
Regards,
Ronnie
Tarawerkz
> On 3 Dec 2020, at 9:27 PM, nug <4d_o...@pghrepository.org> wrote:
>
> Ronie,
> -Go back to the originally damaged structure and try MSC on it
Like Chip stetted, almost all are on discuss forum now. I don’t think support
will help on a v15 db as they no longer support it.
Regards
Chuck
Chuck Miller Voice: (617) 739-0306
Informed
Ronie,
-Go back to the originally damaged structure and try MSC on it again.
-go back to a previous version of the structure (backup)
-contact 4D support
While I personally do not like it….
Also there is a new forum, where nearly ever one is now.
You will get more help/eyeballs on this issue
6 matches
Mail list logo
