Recent posts:
Loren has not published any posts yet.
Recent replies:

No, from what I can tell, the wizard didn't map anything 21600 related at all.  At this point in time, we are just wanting to query the data, not modify it using SQL.  In VistA, the DPT global contains a lot of needed data and so far (we are just getting started pulling this data via SQL) the wizard mapped what we need except what's in data1.  So, if nothing has been mapped for anything 21600 related at all, does that change what you've suggested here? I need to look at anything in the incrementing starting at 1, but it starts at 1 for the incrementing unique. For example, we would see:

first related set:

^DPT(1,21600,1,0)= "2222^5353"

^DPT(1,21600,2,0)= "2222^9898"

^DPT(1,21600,3,0)= "2222^7878"

then next unrelated set:

^DPT(2,21600,1,0)= "2222^1515"

^DPT(2,21600,2,0)= "2222^210000"

etc....

and we need to be able to query data1.  I hope that makes sense what we're trying to do.  We may find more that the wizard didn't map that we need so this is a good example and opportunity to learn how to add more missing subscripts.

 

 

 

 

OK, so here is how it looks:

^DPT(incrementing unique,21600,incrementing starting at 1,0)="constant^data1^^^"

The information we are interested in querying for is stored in data1.  The fields after data1 may or may not contain data but I'm not interested in them anyway but not sure if I need to do anything about them.  We already have the ^DPT global in a single class so it would be nice to just have this contained in the same class if possible.

Thanks

OK. Thank you for the offer to help.  I'll go pull some of the data and look at the pattern of the new subscript compared to what's already there.  If it helps (or hurts for that matter), this data is for VistA and I believe the original classes were created using the FM2Class wizard.

Followers:
Loren has no followers yet.
Following:
Loren has not followed anybody yet.
Global Masters badges:
Loren has no Global Masters badges yet.