Search results

Here is an article from www.unsoftwareag.com: ACCESS ONLINE ENCYCLOPEDIA Article Code: S4 Security of the backend tables ? PROBLEM If you activate the security system on the frontend all database objects are securized. In a split application all tables from the backend file are linked into...

The reason for the bloating effect is the fact that ACCESS stores JPGS and GIF internally as BMPs. Have a look at www.unsoftwareag.com/togwa.htm for alternative solutions.

Overview about runtime issues ACCESS ONLINE ENCYCLOPEDIA www.unsoftwareag.com Article Code: D1 Runtime issues: an overview Transforming MDB files into EXE files It is definitely not possible to transform a MDB- or MDE-file into an executable file since the MDB and MDE-files contain dynamic...

Runtime for 200$ available The cheapest solution is still the MDT-installer that comes with the complete runtime for A2K. Have a look at www.unsoftwareag.com/tomdt.htm for the details.

Maria Estoy haciendo un programita para un supermercadito en Nicaragua. = I am about to create a small program for a supermarket in Nicaragua. Tengo todo listo menos una cosita que nose como hecerlo= I got everything togehter but one detail I do not know how to do it. Me gustaria mandarte en...

List of solutions: This is a wonderful article I found at www.unsoftwareag.com: ACCESS ONLINE ENCYCLOPEDIA Article Code: G3 Why insufficient memory ? Description You can have installed lots of RAM (128 MB and more) on your machine but nethertheless ACCESS crashed after a short period of...

d Did you try to execute a maketable-query? But remember that these temporary tables will bloat your MDB according to their size.

You can not "run" a module, since it is only a container for funcs and subs. Note that only public funcs and subs can be executed from the outside and that form and report modules can not contain public funcs and subs. Here an interesting article from the AOE (www.unsoftwareag.com): ACCESS...

Eventually you need to activate the security system. Be sure to read the MS white paper as well as the security related articles in the ACCESS ONLINE ENCYCLOPEDIA (www.unsoftwareag.com) Here is what I found about the FE/BE architecture: Article Code: G9 How do I split my application in...

You might store the DOC file inside a table thus becoming completely independant. The only problem is the bloating effect, in order to avoid it you need a special wizard like Word!with ACCESS.

Alternative In strongly recommend that you use an Image control to display the graphic files. Furthermore, you should store the graphic file names in a lookup table (minimum e fields: Autonumber/shortName/FileNameWithPath) that feed the combo box: column(0) = displays ShortName column(1) holds...

These are the tools you need: 1. Thorough HTML and DHTML knowledge 2. Excellent ASP knowledge 3. JAVASCRIPT to simulate the intelligence of the ACCESS forms 4. CSS for the graphic interface 5. Intensive testing for performance and security, backup strategy The list is definitely not complete...

You can store the photos, but you need a special wizard, here is a link with some alternatives: www.unsoftwareag.com/togwa.htm I use this system since more than one year, integrated it in 4 applications and I am very happy with it.

You have a security problem I strongly suggest that you change the architecture of your application: The frontend has to be a MDE in order to protect everything except the tables and macros. Install one copy of the FE on each client. If you want to more security, you have to read the MS white...

There is plenty of information about the runtime issue in the ACCESS online encyclopedia at www.unsoftwareag.com

The runtime version of Access2000 is still available with the MDT2000 toolkit at www.unsoftwareag.com/tomdt.htm ! Not only that it is way cheaper than the Developer version, but it comes with a much better installer than the "PDW".

There is plenty of information about this topic in the ACCESS Online Encyclopedia (www.unsoftwareag.com) and www.unsoftwareag.com/togwa.htm.

You could also store the DOC-file inside the table, but in order to avoid the bloating of the MDB you need a special wizard. I use Word!With ACCESS from Universal Software since 2 years but there might be others.

The problem is definitely the temporary tables. Once they are deleted they still require space inside the MDB file. Only compacting (releases up to 80%) or decompiling (releases 100%) will help. I strongly suggest that you de-locate your temporary tables either in a linked MDB or - MUCH better -...

This is the no.1-problem with Access 2000: Check the references in the VBA window. One of them will be marked as "missing". The only solution is to re-link the defectous reference. If you want to avoid this problem then you need to make sure that the referenced files have all the same: -size...