>Hi all,
>
>In my development of a extended version of the Task List Manager I have encountered a strange behavior. When my tool opens a PRG to a specified location, VFP places a Shortcut marker. It doesn't always on the line I specify, generally near by. The problem is that VFP is not recording it in the FoxTask.dbf, but does seem to be recording the position somewhere else. In doing this it will throw an C5 error, The Help file mentions a internally, via the EDITSOURCE() function.
>
>
>You can pass cShortCutID without any additional information and have the editor open at that location. The cShortCutID is the unique ID value for a shortcut record stored in the Foxtask system table (_VFP.FoxTask). The Task List application uses this table to ensure that it can get the latest line position of the shortcut. Visual FoxPro maintains, internally, current shortcut information, but only writes line position updates to Foxtask when a file is saved.
>
>
>The same behavior occurs, only on occasions, whether it is opened with the EditSource() or a Modify Command in ExecScript().
>
>Normally, I would have like this, but ever so offen (too offen), VFP throws a C5 error.
>
>The question is "What internal source is VFP maintaining?" I believe it may be the root of the C5 error. I was told that many of the sources of C5 error are memory overflow issues (like a stack overflow.), but I may be mistaken.
>
>I know it is not the FoxTask.dbf that is holding the Shortcut information only. I hace deleted and packed the FoxTask.dbf and the Shortcut continues to reappear in the Code editor and the FoxTask.dbf.
>

The first two places to look I can think of are FoxUser and the Registry.

Tamar