Dissapearing Background

[Guest]

I have a form with a .gif as the background. When i put an unbound textbox
onto this form everything shows up fine in the print preview nd when printed
out. But, when I throw on a bound textbox, the image dissapears in the print
and in the print preview.

Any ideas why?

 

[Guest]

Forms are not really for printing. Reports are for printing.

 

[Guest]

But I need the ability for the users to insert text that isn't supplied by a
previous form...and as far as I know, a report won't work for that.

UPDATE -- I discovered that once I changed the forms record source from a
query to a table, the textboxes show the correct information and the image
shows, but I need multiple fields from multiple tables.

Any Ideas?

 

[Guest]

How and where do they insert this extra text?

But I need the ability for the users to insert text that isn't supplied by a
previous form...and as far as I know, a report won't work for that.

UPDATE -- I discovered that once I changed the forms record source from a
query to a table, the textboxes show the correct information and the image
shows, but I need multiple fields from multiple tables.

Any Ideas?

 

[Guest]

The database is for insurance brokers to fill out multiple applications at
the same time. The generic information from all of the applications is
collected into one form bound by a query of multiple tables.

Upon submission, the program will call up the specified applications, fill
in the information it has collected, then the user will need to supply the
information that is specific for each individual application.

I am needing to capture this information also, so that future applications
for the same client will already by populated. Is it possible to do this in
a report?

Hope I described that okay!

 

[Guest]

You described it well. Reports are not for entering data. That is what
Forms are for.

I think what you need to do is create a table that will contain a record for
each application. The record should contain all the data elements required
for an application. Then your form should be based on this table. The
generic information could be retrieved programmatically in the Current event
of the form. This is a bit over simplified, but it is the basic concept I
would consider.
Once you have the data entered for the applications, use a report based on
the table to print the applications you want.

 

[Guest]

I think I understand what you are saying, but these applications are LONG!

A single table for each application probably wouldn't have enough fields to
hold all of the information. Isn't there a field # limit?

If I was able to break it down into multiple tables that would be okay, but
I can't use a query as the control source of the form, or the "application
image" background disapears.

I know there has to be a way to do this...