!Type

Question

2010.accdb:  In a complex report - - I am seeing !Type in unbound fields sometimes.   The unbound fields are a calculation involving a DLookUp.

The odd thing is that is seems intermittent, and I can't intentionally cause it to occur - but more odd is that it occurs due to scrolling.  The calcs will be displayed ok - until one scrolls down - and then the !Type occurs in a few fields.... and sometimes they will clear and again display the calculation but other times not....

It is a split db in test mode so only a single user and both front/back files are on the same PC at the moment.  So the network is not an issue.

When it does occur - I have attempted to check each of the parameters of the underlying calculation and they all seem okay (haven't found any unexpected nulls, etc....)    I haven't been able to determine yet if it is due to the amount of data involved.  There are a lot of aggregate queries involved.  So for instance the report could involve 5 records or 500 but not more then that...

Thought I would put this out there and ask for any thoughts on this topic.  Thanks.

Answer 1

If it only occurs in unbound fields, then it's not the queries in the reports Record Source. I would check the the DLookUp calculations to see if any of the fields, tables or criteria are looking for a field named 'Type', because that is what the error appears to be looking for. Also remember that 'Type' is a reserved word in ACCESS, so if you have a field named "Type' in any of your tables, that will be a problem and the field name will need to be changed in every table, query, form and report that references it.

Answer 2

hmmm interesting input; while I don't think there is a field name Type - - I will have to go back and check to be 100%

I wasn't even thinking along those lines so it's a good suggestion.

I was thinking that !Type is sort of like !Name where it can't find the data or possibly is a type mismatch....

btw: the report itself is unbound; it contains 6 sub reports; all independently unbound and then about 20 fields which are all calculations based upon values coming from the sub reports, or the DLookUps

Answer 3

You said "...but more odd is that it occurs due to scrolling".

What scrolling? Are you using a scroll bar within the report itself and trying to scroll through data with it? The subreports should display all the data anyway as long they have their Can Grow and Can Shrink properties set to 'Yes'. You should not need to scroll anything in a report.

Answer 4

Point of clarification:  are you seeing "!Type", or "#Type!"?  I assume the latter, but I could be wrong.

Technically, calculated controls aren't "unbound", they're just bound to an expression.  I take it that's what these are.  Can you post the expression that is occasionally giving the error?

---

Dirk Goldgar, MS Access MVP
Access tips: www.datagnostics.com/tips.html

Answer 5

after these questions I went back to the development PC - and now cannot get the error to occur.

It was happening across a couple of days intermittently as described, and each day the PC was turned off - so I don't think the reboot is the reason it is not happening now - - I will just have to keep an eye out on this.  If nothing in another day will marked solved I guess.

DG: - am at the age where your question makes me wonder about my memory and so now I'm not sure if it was !Type or #Type.... sorry

LE:  - yes to be precise all fields are indeed bound in the sense that they have a formula in their control.  As the main report itself is unbound those text fields can't be bound to the report's record source but they all do have a formula.

       - the scrolling was indeed just the main report's scrolling - it is fairly wide and can be pretty deep - - and it was odd to see a text field change when one scrolled.  I've seen "blinky" refresh behavior in the past on a variety of PCs I've worked at - when scrolling - and tend to chalk it down to the graphics card; but never saw the text box change back & forth from a value (calculation) to the error code.....

Answer 6

Hi msdnPublicIdentity,

Does error occur again or the issue get solved?

If issue get solved then I suggest you to mark your last post as an answer.

It will help us to close this thread and It also will be helpful to other community members who will meet with same kind of issues in future.

If the issue is still persist then let us know about it, We will try to provide further suggestions to solve it.

Thanks for your understanding.

Regards

Deepak

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].