Recent content by dblake

Like your short & neat question!<br> We had to make the switch to SQL since Access('95) couldn't handle the volume of users and records, although it is a excellent and user-friendly program. Nowadays they are optimizing the Access-SQL interfaces so that keeping Access as frontend (retaining your...

Well... sounds like solving this one is going to be a breakthrough! I don't think I have much help, but some ideas:<br> <br> If it runs fine on your PC, and not on someone else's, then check out their user rights/permissions. Are you sure you don't have ANYTHING in a form or table or code or...

One answer is to use the Tools, Office Links, Output to Ms Word option, and save and print it from there.<br> <br> Another is import the report into an new, empty database - (if having a file is all you want, but I don't think so!)<br> <br> Fax s/w is sometimes setup in the Printers Folder...

I haven't done it, but you can give it a go:<br> Delete the old system.mdw file and create a new one - but it means you will have to re-setup the whole permissions structure though... <br> <br>

Haven't tried it out yet, but I guess the following will work:<br> <br> Copy the front end to each users' PC; the backends I persume reside on a server, or on one of the users' PCs.<br> <br> At this stage the frontend can be linked to any one of the project backends - the linked one will be the...

I started working on Access and programmed the normal way, making the following declaration:<br> <br> Dim Rst as Database<br> <br> Further on I have a statement:<br> Me!txtTime = Date<br> <br> When I compile the module, both lines result in the error:<br> Compile error: can't find project or...

If SQL server is on a different maching, using the network, you have to configure it to use the same protocol your PC is using. TCP/IP is preferred. Your Client must be setup with the Client Utilities, and with the same protocol in the Network tab, as well as the Client Configuration.<br> You...

Have you ever tried the SQL view? The SQL is what the database engine actually understands - the Design view merely creates SQL from your input, and therefore sometimes creates the WRONG SQL, or SQL that takes ages to execute!<br> <br> Back to your question. I suggest using Copy, Paste in...

We recently had to make the jump to SQL, since Access was giving us strange locking errros when doing update queries on a table that had only 32 000 records (but 20 users!).<br> <br> MapMan's advice refers, since it took me about 6 months of idle fooling around with SQL to get the hang of it...