Search results

I think it's a matter of the frequency the default value changes. If it changes over time maybe I'll use it in a table and give the users the option to change it themselves. But if it changes only once a year, than I think it's a lot faster to just assign it as a default value in the table...

completely with you on that one.

Thanks for the clarification.

@neilg: it took me some time to understand it at first, sorry for that. but isn't this not exactly normalizing? if I have 50% corporate clients and 50% private, isn't it a lot of "space" in the table for nothing?

Thanks, worked like a charm. And another small question: I've set up my input masks on the tables, but now I see many discussions on the web regarding it's better to put the input masks on the forms. Which is better practice?

Perfect guess. I've just copied another label and it appeared on the top left side and I haven't seen it's not part of the tab. it drove me crazy for a while! thx a lot!

I've got a tabbed form and a label that I use as a headline for some fields. When I create a new page in the form, the label appears in the new page also (the only one). If I delete it from that page, it also deleted from the original page. how can I tie it to the first page only?

Take a look at microsoft templates that came with access 2007. They do email sending with macros, and maybe it will help you.

If I don't want to set lookup fields in the table, but in the forms. Do I still need to create relationships between the fields or this can be done directly from the form? I'm asking because when Access create lookup fields in tables, it does create relationships. Let's say I have a table of...

Another idea: what if i use one table only for all the clients. They're basically the same. only difference is that on corporate clients I need to save the company name and a second contact information.

Hi Doc_man, first of all thanks for the lengthy explanation. I've forgotten how much is the access developers community is around the world. I clearly see your point. But what if I want a unique ID for every client that will follow the same logic? how can add this into the database if I've got...

I can't quite follow you. Why would I have two sets of numbers for clients? it can only confuse the users. furthermore If I will have more than 2 types of clients, then I would have to rewrite many queries, instead of just running every query with the tblClients at first.

@neileg: I'm saving different information for the corp clients and the private ones. Actually the system I'm working on is intended for a company that runs after school activities in schools and in private events. The corp clients are schools which I need to save info like contact persons...

John, If I create a query that combines all of the information before loading the form, I can use it as my record source and doens't need all of the sub forms? which is the better practice?

John thanks for the reply. You've actually solved me my next question :) But actually I'm more in the level of defining the relationships. So I have ClientID in the tblClients and it's a primary key. Should the primary key in both the other tables should be with the same name and linked with a...

I'm not new to Access, but I've been away from this for a long time (too long it seems). I'm trying to create a clients database that holds info about Corporate clients and Consumer clients. I've got tblClients which hold a primary key of ClientID (AutoNumber) and ClientType (1 for corporate...