Search results

If you tried everything that is proposed in the ACCESS ONLINE ENCYCLOPEDIA then you definitely need to create code libraries.

The OLE commands require the existence of a OLE control on a form therefore the code does not work properly in your code (I am surprised that no error message occurs!).

Have a look at the Graphic wizard (ACCESS Powerup) at www.unsoftwareag.com.

Maybe there is a solution on the page of the graphic wizard at www.unsoftwareag.com. Otherwise I could only imagine to check with the DIR function whether the file exists and to make the image control invisible if necessary. But I fear that this will slow down the report (depending on the...

I would integrate all documents in any format as OLE objects into an ACCESS table. Then it is very easy to create the necessary logical links between them, you do not have to bother about filenames and locations and different versions. I used this system for example for an international lawyer's...

As long as you use the LIKE operator the query will always be suboptimal even if the field is indexed.

I do not think that the ownwership is the reason for your problem. I suppose that you are calling a function from the autoexec-macro or in the startup form and this function tries to modify (invisibly) one of the system tables. This function might be a refreshlink or something like that (you...

You should really use a report instead of a form to print your data.

I suppose that ACCESS is simply too fast for the third party program. You should experiment with DOEVENTS or (better) the SLEEP command between the SENDKEYS commands. In general, 500 ms are sufficient for the third party programs to respond to ACCESS. On slower computers you might have to...

I remember that I encountered this problem some years ago in Access 2.0. The reason was the fact that the data from the Main form was not requeried when the subform got the focus. If a new records was displayed in the Main form and I wanted to create a record in the subform then this was not...

Have a look at the ACCESS ONLINE ENCYCLOPEDIA (www.unsoftwareag.com). In the "forms"-section there is plenty of information about multiselection boxes.

There are multiple ways to solve this problem depending on your application. The easiest way is to use the SENDKEYS command (with a error trapping procedure to avoid headache).

Did you try "ME.REQUERY"?

You have to use the value of the combo-box and create a SQL-string that will become the recordsource of your form (afterUpdate-Event of the combo box). Example for a single date: sub_yourcomboBox_afterUpdate() dim strSQL as string strSQL= "SELECT * FROM INVOICES WHERE "_ & "INVOICE_DATE =...

You could ask Jack.Richardson@UnSoftwareag.com (one of the developers of the MDT-2000).

Just use the itemsselected property to create the SQL string for the creation of a recordset. This recordset can be transformed into a query with its name-property (see ACCESS ENCYCLOPEDIA for sample code)

Apparently it is not so difficult to realize a slide show on Access forms. The MDT-2999 installer that replaces the PDW in the runtime version contains this as a standard option. Since you can modify the display time I suppose that the timer event is used with a special code that displays the...

This is the classical example for a situation in which you have to violate the rules of normalization: The current prize has to be copied into the orders (details) table. This is the only way to be able to change the price of the product without changing the price in each and every old order...

Yes: Activate the security system.

I think that there is no sense in further research. In this case I do the following: -copy the code segment with the weird breakpoint -delete it -save the module -open it again -re-insert the code -save it again.