Search results

Sure However I think you are not breaking the thought down enough. First of all the images themselves should not be stored in Access as this will bloat your database bigtime. So you are going to want the webcam or othter device to take the picture and save the file on a hard drive someplace...

DoCmd.TransferDatabase acExport, "dBase IV", "c:\Wherever", acTable, "tblMyTable", "MyNewTableName", False

Yup your right it will only show the one value. I believe you are looking to next the second combo and that is fine. Basically you make the second combo with both the ID and the Name fields in it. Go into design view for the second combo's Row Source and under the ID field put the first combo...

email me if you want a demo of what I think you are trying to do.

I hope I understand what you are doing? The thought I have on this is that a combo box can contail multiple columns. One combo box can contain both the ID and the name in it. So a second combo may not be necessary to what you are trying to do. Also though a combo can have multiple columns...

Generally as a rule you wouldn't do this, though there is the occasional exception but it is very occasional. It is a matter of saving space vs creating a mathematical equation. In your table do not save the total that you want. Make up a query and in the query add a field with the...

Sounds to me like you have over thought this one. In your premises table you should have a field that will contain either the value "Liquor" or "Kava". This will get rid of the "Kava" table. You then make a combo on the form with a list containing both Kava and Liquor. Next create a query...

The output formats for this process are: acFormatDAP; acFormatHTML; FormatRTF; acFormatTXT; acFormatXLS. There is not one for Word specifically but Word can open the RTF and TXT formats as well as the HTML for that matter. You have to look at it this way. These formats are standards that can...

'LTrim([tblF006.Business Unit]) is a very basic part of VBA. When a reference is not right the VBA reacts by not allowing event he most basic of code to operate. You have to have a reference that is not correct

Yes the test machine is missing a reference that is used on your developement machine. If you go to any coding window on the new machine and then go to Tools menu and then References there will probably be something in the top of the list that is missing. It may just be a version issue...

Sounds like when you enter the record the first time you are applying a filter. As a result the record source will not have the second record you are looking for. You simple need to remove the filter before opening the form for the second time.

Exactly - that is what it is for. The Developers Edition of MS Access allows you to create a database to distribute to others even if they do not have Access on their system. Now there are some restrictions as to what they get because they get what is known as a run time version of Access...

You could simply create the who thing in Access and distribute it freely to all other users IF you create it using the developers edition of Access. Email me if you need a hand with that issue.

Have you checked to make sure the regional settings in the control panel is the same on the computer that it will not work on as it is on the others?

Sort of Basically just go into the data tab for the form and do not allow additions. This is disable but not remove the button.

Database problems Nice to meet somebody else from Ontario. Sounds to me like you need some sort of variant using the format(now(),"yyyy") or something of the like. If you would like some feedback or for me to have a look at what you have drop me a line. I have time to kill. :)

Sure do: The problem is that you should not be using a DLookUp to assign the values to the sub forms. Instead you need to link the sub forms to the master form. This is done on the data tab for the sub form "Link Master Fields" and "Link Child Fields" Email me a sample if you can not do it...

Go to Tools Startup and pick the opening form from there.

Well first of all I don't think you should be storing a value that you can calculate later. Saving the QtyRemained in the table will increase the size of the database needlessly. Taking the total QtyReceived and subtracting the total QtyDisposed for any one MaterialName will always give you...

Personally I would never have a field in a table that is based on a calculation. If you have a field where CD's are added to the inventory then a DSum on that field would give you the total of CD's available. Since you have a field for CD's going out, if you DSum those and subtract that amount...