Search results

Ah! Now I see. (btw, regular view for forms is called form view. ;)) I believe the only way to have a different form header colour is to disable the form's picture (Or maybe you can mess around with the different settings in the FORM'S properties.) If you compare the Form's properties to the...

Hm, Can you throw up a screenshot of the form (in design view)? Using a wizard doesn't limit you to change any properties. Make sure you click the background area and then change the background colour.

Um. You can change it's COLOUR via properties. If you want it to be a picture, you don't make it to be apart of the background. You put a picture object where you wish it to be and put anything else on top of it.

Something you should try might be either (1) change the bound column to 1 and see what it's actually binding with or (2) change the column widths so they both are visible. If you are only referencing one field, why even bother with making the first "invisible"? You can use a SELECT statement...

Sounds like a missing Record Source. Do you have one set? Design view of the report.. Properties.. Data tab.. Is the appropriate Record Source entered?

You're welcome. Glad we could help out. So you got it resolved?

Hm. Change the ANDs to ORs after Is Not Null. If that doesn't work.... *thinks*

Right, but in the example it wasn't developed far enough to do any of those things yet.

About 2am now. I'll be on tomorrow to answer any more questions you leave (if they aren't replied to already)! Or PMs too. :)

Oops. One of the "TEXT" fields needs to be changed to MEMO. If memo is too small.. then you'll need to use OLE Object. Goto design view of your table and make the above changes.

It's not that bad after you get some practice.. especially with the guru's here! :cool:

Sure! It's saying "I want (select) data from the tblGenre table but I only want everything in the field txtGenre." Those types of statements can get pretty long at times. That probably is the simplest they come. However most I use don't get incredibly long.

Definately. Just most of the time you had a good reason to create the relationship.. so you probably won't be doing too many deleting of relationships. Especially with a well-used elderly database. :p

The relationship is not needed to perform this task you started the thread for. In this instance, a relationship just helps speed up the database a teeny tiny bit. I did create the relationship first though.. just good practice to create a relationship as soon as you have related data and...

You can do it too! Quite simple really. Click the line inbetween the objects (tables in this case) and click DELETE. 1) Click txtGenre (from tblGenre) & hold the button down. 2) Drag it over to txtGenre (in tblMovies) and let go. (A window will pop-up.) 3) Check Enforce Referential Integrity...

Here ya go. Check out the attachment. You can even start using that and add to it. Whatever you want. :) Edit: Oh.. It's an Access 2000 database. Is that what you are using? It should work in anything but Access 97. :eek:

One minute while I whip up an example. Please.

Ohh! Just joined the forum? Welcome! Hope you visit often. :D Make that four posts. :o

Now that I think about it. It would be a good idea to have a table just for the available genre's. Then you could use it as a Row Source when you enter more movies to your database. And Limit to List to prevent spelling goofs. Anyways.. hope the three posts don't bother ya. ;)

Another note.. if you have a table that already has a bunch of movies entered with all their information. You wouldn't have to create a new table just to list the genres. If you have a table something like this already.. (Example) (title)Star Trek (genre) science fiction (title)Star Trek II...