Search results

Yep. Unfortunately to learn about NORMALIZATION is a "must" for you. So open the link (or google yourself) and try to understand the concept.

Show us the DB structure. Have you knowledge about this ? Database Normalization and Table Structures - Microsoft Access / VBA

Not sure what you intended to do but from your explanation the AllowDeletions property of the form should do the trick. So create a button for record deletion. When this is pressed ask for password. If password is OK set AllowDeletions to True, delete the record then restore the AllowDeletions...

While I'm not comfortable with SQL I developed other technique in order to solve situations like this: I create an working query that do what is supposed to do. Then I copy the SQL and paste it in VBA. Then I tweak this in order to insert variables as criteria. For sure the code is less...

I found that leaving the entire detail background of the form with continuous action to take was causing certain images on the form and the Properties window to flicker intermittently. No need to sophisticated code in order to avoid this. Just check the visibility before change it and change...

Learn this Database Normalization and Table Structures - Microsoft Access / VBA then redesign your DB.

My point is: Say to the client: I can do THIS. Then ask he: How much you pay ? My experience said that you will gain more than you expect.

I think that somewhere in your project you have one more "pintUserId" declared as public variable. Do a search and look to all places where the "pintUserId" appear.

While it is possible to silently subscribe to a thread, it is also possible to tell something, isn't it ? :) OK. I'll tell you the Edison's story (not all, of course, just the story where Edison make first money as inventor). His boss ask Edison, in order to buy the invention, how much money...

Try to save in a previous version of Access. I use 2007 but better is to save in 2003.

1) Click your subform (in the main form - design view) and take a look to the "linked fields" (properties panel). I don't make a selection about date. In my opinion is not necessary. While you see all the appointments for a person, sorted by date (ZA), should be very simple to scroll down the...

Now I must go to my workplace. Try to recalculate the AppDuration. The key should be the DateDiff function. Let me know if I am close of your needs.

Ok ?

Of course you can. Be aware that I use 2007

Hi. Not sure but, in my opinion should work from Access. (From Excel work for sure) http://www.vbaexpress.com/kb/getarticle.php?kb_id=339

Happy that you solved the issue, but I suspect that this is not the right way. The duplicates should be stopped at table level, not at form level. So, do not allow duplicates at table level and, doing this, the form will no longer accept duplicates.

In attachment you will see a combo. Look at the properties of this combo, especially under "Data" tab but also under "Format" tab (ColumnCount and ColumnWith properties) Is this what you are looking for ?

First of all seems that you need to understand very well this: Database Normalization and Table Structures - Microsoft Access / VBA Second... No. Is no need to have 2 tables for "expenses". Use a single table but add one more field "IsFixedExpens" (or IsVariableExpens) of type Yes/No and fill...

Too much text in your post (for me :) ). Read this: http://www.fmsinc.com/microsoftaccess/Forms/combo-boxes/index.html

Don't understand what you mean when you speak about "child record". The children records should be stored in a child table. And this table should be used as subform in the main form. Access will do the rest for you.