Databases
StackOverflow2013
Postsdbo
POWhen called from an Excel VBA UDF, Range.Precedents returns the range and not its precedents. Is there a workaround?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhen called from an Excel VBA UDF, Range.Precedents returns the range and not its precedents. Is there a workaround?
    primarykey
    data
    text
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjtolle
    1. USjtolle
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhen called from an Excel VBA UDF, Range.Precedents returns the range and not its precedents. Is there a workaround?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhen called from an Excel VBA UDF, Range.Precedents returns the range and not its precedents. Is there a workaround?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhen called from an Excel VBA UDF, Range.Precedents returns the range and not its precedents. Is there a workaround?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI did find this on Charles Williams's excellent site (http://www.decisionmodels.com/calcsecretsj.htm): "You cannot make a VBA UDF which directly...uses...PRECEDENTS". However, I'm trying to get the precedents of a `Range` *other* than the one calling the UDF - i.e. get the precedents of the UDF's *argument*. That doesn't terminate the UDF call; it just returns the argument, not its precedents.
      singulars
      1. POWhen called from an Excel VBA UDF, Range.Precedents returns the range and not its precedents. Is there a workaround?
      1. USjtolle
    2. COPlaying around with this a little more, I notice that this happens for *any* range, not just the argument to a UDF. I.e. a hardcoded function that returns `[c11].precedents.address` also just returns "$C$11" when called from thw worksheet. I hate calling things like this bugs since it's not really the intended use of `Precedents`, but it's so annoying that it's not documented...
      singulars
      1. POWhen called from an Excel VBA UDF, Range.Precedents returns the range and not its precedents. Is there a workaround?
      1. USjtolle
    3. CO+1 great question. Dealing with precedents, especially off sheet ones, is a rather arcane process.
      singulars
      1. POWhen called from an Excel VBA UDF, Range.Precedents returns the range and not its precedents. Is there a workaround?
      1. USbrettdj
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload