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 there

https://discuss.4d.com <https://discuss.4d.com/>

Chip

> On Dec 3, 2020, at 5:42 AM, Tarawerkz via 4D_Tech <4d_tech@lists.4d.com> 
> wrote:
> 
> Hi All,
> 
> I would like seek advice on an issue I encountered with a v15 structure file 
> which has been in use for a long time.
> 
> Recently, when I logged in with the designer password to make some amendments 
> to the code, I encounter a memory allocation error on a resource blob.
> So I did a structure repair and compact using MSC utility.
> 
> After the repair, the original error is resolved but a new error appeared in 
> its place,  
> This time it is an attempt to read beyond end of stream (error code 200).
> Subsequent repairs of the structure file does not remove the error.
> 
> The issue is data independent as it also appears with an empty data file.
> If I were to log in as a normal user (not the designer account), the error is 
> not encountered.
> 
> May I ask how I can recover the structure in this instance?
> 
> Regards,
> Ronnie
> Tarawerkz
> 
> 
> 
> 
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> New Forum: https://discuss.4D.com
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **********************************************************************

**********************************************************************
4D Internet Users Group (4D iNUG)
New Forum: https://discuss.4D.com
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**********************************************************************

Reply via email to