Search results

I assume that you have placed 4 picture objects on your page which gives you four of the same picture. You would need to set you page to 4 columns and place only one picture object Go to Page setup under File with the report in design view. Select the columns tab and change the number to 4...

The first thing to do is set the forms source as the table or a query of the table where you store the data. In design view, do this by moving the mouse pointer over the icons in the Form Design toolbar until you see properties. Select this icon and add the table/query in the Record souce...

To continue with what Rabbie said, look for Functions (Alphabetical) in Help.

Try this: http://www.mvps.org/access/forms/frm0015.htm

Are they using a form to do this? If they aren't they should be. You can lock individual fields in a form so that the user can't change them. This is another good reason to use forms for data manipulation and not allow users to go directly into the table.

IMNSHO an Access form's beauty is in how easy it makes it for the user to interface with the db. Getting asthetically beautiful is of no use to the user. A form that is intuitive to the user is what you want. If you're doing something for a client or your boss maybe put the company logo on it...

If you don't see the db window when opening with the shift key, hit F11.

But they are fairly easily translatable one to the other.

I would think that a family table with FatherName, MotherName, FatherWorkPhone, MotherWorkPhone, etc. would suffice since you would have a father and mother, a single mother or a single father for a child. The only problem would be a man who fathered two children the same age with two different...

Try the Form scaling/resizing tool link here: http://www.mvps.org/access/general/gen0002.htm Hope this helps.

My guess is that most of us deal with importing Excel file and not much else. Once we get the file into Access why go back. We just don't need to display a spreadsheet in Access.

As far as normalization goes #6 covers that. Access Help is extensive and it speaks American, English, Aussie and Kiwi.

I doubt you'll read this but you'll get the same response on just about any forum on double posts, accidental or not. What is the official mourning period for a lost member?

For what he wanted, Windows permissions are the easist to implement. He said he wants to "prevent people viewing and altering tables, queries etc." The easist way to do that is to keep them out of the db period. Viewing table data is the most basic function of a db. If I'm wrong about that...

I believe you'll find that the Calendar control is like any other in that you can pick the format and input mask. That being said you should scrap MS Calendar Control for better ones like the ones whose links are found here: http://www.accessmvp.com/JConrad/accessjunkie/calendars.html

The simplest way is to use Windows permissions. Have your IT give you owner permission on the BE's folder. That way you can assign users permission as you see fit. That was the way I controlled security on a multitude of dbs I had written for my company. There was a Personnel folder to which...

'69 Camaro contributed this on another forum: Error #3048 is usually caused by your database application trying to handle too many tables at the same time. There are 2048 "table handles," or TableID's, available for Jet 3.51 and 4.0 (1024 TableID's for Jet 3.0 and 3.5) that Access requires when...

Do you want to enter the shift and date in the main form and then enter for example each person who works on that shift and theri hours on that date in the subform? If you do you need the subform to be continuous and the main form to be single. Every time you enter a new record in the subform...

To answer your question, you have to find the database to which the db you are using and if you do, in Access with your db opened select Tools, Database utilities, Linked table manager. In the linked table manager, select Select All and the check the Always prompt for new location and the OK...

If no product has components used in another product, I would have two tables. First would be the tblProducts with ProductID as the primary key and other information as needed. The second table would be tblComponents with ComponentID as the primary key and ProductID as the foreign key. If...