Doesn't alter my comments.
Doesn't alter my comments.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
I understand, just thought you would like to see what we were talking about.
Thanks for the help.
Okay, you have a plan for fixing?
The sequence string is saved with every record on the main form?
A VBA custom function might be able to get the record's sequence from the string. Something like:
The function would be in a general code module and can be called from a query, like:Code:Function GetSeq(intTask As Integer, strSeq As String) As Variant Dim aryTasks As Variant, x As Integer GetSeq = Null aryTasks = Split(Replace(strSeq, " ", ""), ",") For x = 0 To UBound(aryTasks) If intTask = Val(aryTasks(x)) Then GetSeq = x Exit Function End If Next End Function
GetSeq([TaskID], [Sequence]) AS SeqID
That query would be a join of the parent and dependent tables so that the Sequence field is available.
Be aware, custom functions called from query can cause slow performance.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
I did not have a plan for fixing but what you have provided sounds like the best option forward.
The sequence string is saved with every record on the main form.
I am not too concerned with slow performance as much a visually see the tasks in a sequence for the user.
Thank you very much for this!
If you use the query as RecordSource for subform, do not use INNER JOIN.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.