So here's where i'm at now:

[Guest]

Current issues:

scrollbar doesn't work on the listbox control.
Its currently attached to a query that allows one to filter the records shown.
you can pointer key through it, but using the mouse no scrolling back up once
you've scrolled down -- its a one way trip.


Printing issue: i have no idea what causes this. some of the text is missing.
There are no visible or hidden fields sitting in the middle of the page, yet
some of the field names are cut off. The entire text label and field name
are displayed when in design view, and seem to have enough room. but when
i print it out, it cuts off. Is this something to do with the max field
length
or something?

also if any field within any record is set visible, it prints all of the
records as if ALL of them had that field visible (even though some of those
fields are null, and in fact, invisible, if one scrolls through them.)

Import issue:
My splash page opens up and runs a macro to: import the data. works just
great.
copies it into an append table. works fine. When it goes to run a Query to
map the data proplerly from the append table into the main table, it says
tha i don't have the proper activex control, or no permissions to use it.
this is using the DoCmd.Query [queryname]. Is this not how i should be doing
this in a macro
running?
Furthermore, when i run the Query by hand, after the macro fails, i'm still
getting
loads of warnings about data integrity and the like, even though both tables
and all their fields match in their validation rules, text, required
settings or
non-settings, type, format, and so on. Zero length, etc. All identical.

 

[George Nicholson]

1)

DoCmd.Query [queryname]

Simply won't be recognized. "Query" is not a method of DoCmd. You probably
want:
DoCmd.OpenQuery [queryname]

2)

also if any field within any record is set visible, it prints all of the
records as if ALL of them had that field visible (even though some of
those
fields are null, and in fact, invisible, if one scrolls through them.)

Huh? Sorry but this could be read to mean any number of things. When you
scroll through the report you have records where fields that were invisible
on screen are visible on hardcopy? More specifics about what you are seeing
(and where) vs what you expect/want to see, please.

Any chance that this report is based on a form and you expect the report to
automatically behave the same way the form did? Don't. All that "base this
report on a form" does is give you a starting layout. Any other
functionality will need to be added. Code behind the form was probably
copied to the report as-is, but most of it won't do anything without heavy
editing since there are so few Events that the 2 have in common.


3)

i'm still getting
loads of warnings about data integrity and the like, even
even though both tables
and all their fields match in their validation rules, text, required
settings or non-settings, type, format, and so on.

I wouldn't bet on that. If you are getting validation rule errors you *are*
getting them for a reason. Period. Those do *not* happen by accident. You
just haven't found the cause yet. For instance (from an earlier post):

One of my yes/no fields, which is a text field inthis case, defaults to 0
instead of yes, or no.

That makes no sense. A Yes/No field *can not* be "a text field". If you have
a field with a Yes/No datatype then it is a Boolean field and can *only*
hold one of three values: Null, 0, -1. What *displays* in that field
depends on how you set its Format and Display control properties:
0 = False, No, Off (unchecked)
-1 = Yes, True, On (checked)

Keep in mind that what actually gets stored and what is displayed can be 2
entirely different animals and the validation rules apply to the *stored*
values. Since there is no such thing as a "text" yes/no field, if you are
trying to append text values to this field it could easily be the cause of
the validation errors since text values aren't acceptable. Date fields and
text values representing dates can be another trap similar to this that
requires datatype conversion in the Append query.

If that is the case then *if* you have this field set to Required=Yes and
DefaultValue=0 (or =False or=No), then when you tell Access to do the append
in spite of the errors, it will fill this field with 0 regardless of what
your incoming data contains. This is easy enough to test: do any 'True'
values in your incoming data survive the append?

--
HTH,
George

Current issues:

scrollbar doesn't work on the listbox control.
Its currently attached to a query that allows one to filter the records
shown.
you can pointer key through it, but using the mouse no scrolling back up
once
you've scrolled down -- its a one way trip.


Printing issue: i have no idea what causes this. some of the text is
missing.
There are no visible or hidden fields sitting in the middle of the page,
yet
some of the field names are cut off. The entire text label and field name
are displayed when in design view, and seem to have enough room. but when
i print it out, it cuts off. Is this something to do with the max field
length
or something?

also if any field within any record is set visible, it prints all of the
records as if ALL of them had that field visible (even though some of
those
fields are null, and in fact, invisible, if one scrolls through them.)

Import issue:
My splash page opens up and runs a macro to: import the data. works just
great.
copies it into an append table. works fine. When it goes to run a Query
to
map the data proplerly from the append table into the main table, it says
tha i don't have the proper activex control, or no permissions to use it.
this is using the DoCmd.Query [queryname]. Is this not how i should be
doing
this in a macro
running?
Furthermore, when i run the Query by hand, after the macro fails, i'm
still
getting
loads of warnings about data integrity and the like, even though both
tables
and all their fields match in their validation rules, text, required
settings or
non-settings, type, format, and so on. Zero length, etc. All identical.

 

[Guest]

All right. no, this isnt' a report. As i'm looking through records on my
form, lets say that the record i'm looking at has a checkbox set to true, the
field associated with it is visible, and there's something written into the
field. Fine. This code
Private Sub Check35_Click()
Me.Text82.Visible = (Me.Check35 = True)
End Sub

and this code

Private Sub Form_Current()

Me.Check35 = Not (IsNull(Me.Text82))
Me.Text82.Visible = Me.Check35
.....
end sub

make sure that the checkbox can't be checked unless there's something in the
field, and that the field can't be visible if the checkbox isn't checked.
so if you click the checkbox and scroll to another record without putting
something in the field, the checkbox unchecks itself.
so. lets further say i wanted to just print some of these records. so i go
into the print "page setup" and tell it i want to print records 1-5. it'll
print them all right.
However. If any one of the records that i'm printing had any of the fields
set to visible at the time (had data in it, and its associated checkbox was
true), it will print every one of those records as if they all had that field
visible, even though it prints the other records with that field blank,
because in fact, they have no data in them.
if you'll give me an email address, i'll be happy to send you some
screenshots, because yo ucan see the same problem when you're scrolling
through the records in print preview.

1)

DoCmd.Query [queryname]

Simply won't be recognized. "Query" is not a method of DoCmd. You probably
want:
DoCmd.OpenQuery [queryname]

2)

also if any field within any record is set visible, it prints all of the
records as if ALL of them had that field visible (even though some of
those
fields are null, and in fact, invisible, if one scrolls through them.)

Huh? Sorry but this could be read to mean any number of things. When you
scroll through the report you have records where fields that were invisible
on screen are visible on hardcopy? More specifics about what you are seeing
(and where) vs what you expect/want to see, please.

Any chance that this report is based on a form and you expect the report to
automatically behave the same way the form did? Don't. All that "base this
report on a form" does is give you a starting layout. Any other
functionality will need to be added. Code behind the form was probably
copied to the report as-is, but most of it won't do anything without heavy
editing since there are so few Events that the 2 have in common.


3)

i'm still getting
loads of warnings about data integrity and the like, even
even though both tables
and all their fields match in their validation rules, text, required
settings or non-settings, type, format, and so on.

I wouldn't bet on that. If you are getting validation rule errors you *are*
getting them for a reason. Period. Those do *not* happen by accident. You
just haven't found the cause yet. For instance (from an earlier post):

One of my yes/no fields, which is a text field inthis case, defaults to 0
instead of yes, or no.

That makes no sense. A Yes/No field *can not* be "a text field". If you have
a field with a Yes/No datatype then it is a Boolean field and can *only*
hold one of three values: Null, 0, -1. What *displays* in that field
depends on how you set its Format and Display control properties:
0 = False, No, Off (unchecked)
-1 = Yes, True, On (checked)

Keep in mind that what actually gets stored and what is displayed can be 2
entirely different animals and the validation rules apply to the *stored*
values. Since there is no such thing as a "text" yes/no field, if you are
trying to append text values to this field it could easily be the cause of
the validation errors since text values aren't acceptable. Date fields and
text values representing dates can be another trap similar to this that
requires datatype conversion in the Append query.

If that is the case then *if* you have this field set to Required=Yes and
DefaultValue=0 (or =False or=No), then when you tell Access to do the append
in spite of the errors, it will fill this field with 0 regardless of what
your incoming data contains. This is easy enough to test: do any 'True'
values in your incoming data survive the append?

--
HTH,
George

Current issues:

scrollbar doesn't work on the listbox control.
Its currently attached to a query that allows one to filter the records
shown.
you can pointer key through it, but using the mouse no scrolling back up
once
you've scrolled down -- its a one way trip.


Printing issue: i have no idea what causes this. some of the text is
missing.
There are no visible or hidden fields sitting in the middle of the page,
yet
some of the field names are cut off. The entire text label and field name
are displayed when in design view, and seem to have enough room. but when
i print it out, it cuts off. Is this something to do with the max field
length
or something?

also if any field within any record is set visible, it prints all of the
records as if ALL of them had that field visible (even though some of
those
fields are null, and in fact, invisible, if one scrolls through them.)

Import issue:
My splash page opens up and runs a macro to: import the data. works just
great.
copies it into an append table. works fine. When it goes to run a Query
to
map the data proplerly from the append table into the main table, it says
tha i don't have the proper activex control, or no permissions to use it.
this is using the DoCmd.Query [queryname]. Is this not how i should be
doing
this in a macro
running?
Furthermore, when i run the Query by hand, after the macro fails, i'm
still
getting
loads of warnings about data integrity and the like, even though both
tables
and all their fields match in their validation rules, text, required
settings or
non-settings, type, format, and so on. Zero length, etc. All identical.