Search results

For a POS application I wrote different codes to open a cash drawer. Is this what you are looking for?

The OLE capabilities of ACCESS have a very big disadvantage: Your database might explode. I had the (bad) luck that different clients asked me to integrate WORD documents and graphic files into an existing ACCESS app. It nearly drove me mad but I had the luck to find a tip in a discussion for a...

1.Is the "signature" a graphic file ? 2.Does it need to be protected? If the answer to both questions is positive, then you do not need to learn anything at all, you just need the Grapic Wizard (at www.unsoftwareag.com) for ACCESS. Els

You might have to re-design your table. You should not store more than one path in one field. Create one field per doc or, if you need an unlimited number of Word docs per record, then you need a subtable that holds the paths (1 field = 1 doc). Maybe you should have a look at the...

It should be possible but there are lots of better (easier) solutions to this problem.

I think that the format of the date is the problem, try the following: dim varDate oldstkdate = DMin("date", "qrygdsout") vardate="#" & format(oldstkDate,"mmddyyyy") & "#" oldstkarea = DLookup("[areaID]", "qrygdsout", "[date] = " & varDate )

I suggest that you give your users only one single possibility to access certain forms. Then it is not only quite easy to close the undesired forms but data integrity is easier to control. On the other hand, for performance and memory-issues it might be more intelligent to keep certain forms...

Alternatively, you could integrate the XL file in your table with the EXCEL! wizard (www.unsoftwareag.com). Then you can open your XL file with one button click.

Bonjour, Alexandre, Voilà comment il faut faire: 1.) you create a module-wide variable mLastOnglet 2.) you use the OnCurrent event of the form like follows: me!OngletName.value = mLastOnglet 3.) you use the OnOpen event of the form as follows: mLastOnglet=0 (la première page du contrôle...

Code snippet for the Keypress-event: select case key case VBDOWN key=0 ' deactivate the "Standard" behaviour ' your code ' and so on!

I do not know whether this information might help you, but I found a very elegant solution for these path-filename-related problems. One of my clients (lawyer) wanted to manage his Word-files with ACCESS. Another (office with more than 50 architects) wanted to manage AUTOCAD files. Several...

Strange behaviour, maybe you will find a hint at the solutions page of the Graphic wizard at www.unsoftwareag.com.

You should try the OnFormat or OnPrint event of the group header. Maybe you find another hint at the solutions-page of the graphic wizard at www.unsoftwareag.com.

Have a look at the "Solutions"-page of the Word-for-Access-Wizard at www.unsoftwareag.com.

I feel that it is a lot of work to write (and to MAINTAIN!) a hand-written list of 30 reports. I would simply use the in-built system tables to read the names of the tables and display them in a 1.) listbox if there is enough space 2.) a combobox otherwise.

How many -forms (with modules) -reports -modules does your application contain ?

1. You set the visible-property of box2 to FALSE 2. On the AfterUpdate-Event of box1 you change the Rowsoure property of box2 according to the choice of box1 and you set the visible-property of box2 to TRUE Note: The rowsource is simply an SQL string

CursorType = adOpenReadOnly should solve the problem.

What questions do you have ?

I think this is the biggest pitfall in ACCESS: NEVER EVER call a field or control NAME. This is a reserved word for ACCESS VBA and causes permanent headache. Additionally, I think that quotation marks are necessary.