Search results

Apologies, answered my own question. For some reason Windows had set the default printer to a label printer and hence the tiny page size :banghead:

Hi, I have a database with reports that print perfectly, I am now using the same database on a different PC and the reports are huge. An A4 page on one computer is twenty six pages on the other with everything scaled up massively. I am probably being a bit thick here but where could the cause...

DoCmd.OpenForm "IndivClients", acNormal, , "ClientNumber=" & TaxpayerClientNo should be: DoCmd.OpenForm "IndivClients", acNormal, , "ClientNumber"= & TaxpayerClientNo

Same here, when the guy came to pump it out I asked him whether he covered the whole country and he said he only worked locally, he stated, and I quote, 'you'd be surprised how many idiots do this'.

Running front and back ends is easier for development. In theory your back end should not need much changing and if required you can just update this out of hours when nobody will have it open. Most updates are done in the front end and you can change the one on your machine and test it...

Why don't you just trim it: 2-8 = 2 2-5 = 2 If they are asking for two to eight years they cannot object to you only having seven, if you are willing to take the pay packet they also cannot be too concerned if you have nine :confused:

I think what is being asked for is the opposite of this, just show relevant decimals so 5.1200 becomes 5.12% and 5.1234 becomes 5.1234%, I am guessing you could trim zeros but it is a lot of effort.

Go to the Database Tools ribbon, select a query and click Object Dependencies, if nothing depends on it, it is presumably obsolete.

Are there two questions here? The problem of using a different drive when the server drive is down for a long period is to just change the location of the back-end through the Linked Table Manager and then distribute new front-ends to all users. Logically this can all be automated. Control of...

I think you are out of luck: General Number: Display the number as entered. Standard: Use the thousand separator; follow the settings specified in the regional settings of Windows for negative amounts, decimal symbols, and decimal places. You can (I think) only change the number of decimal...

In the table store the number as a double. If you do this it should all work without any effort as attached.

Logically you could do this with an update query and copy the records to a second table and delete them from the first. Set the query to run when the database loads. However, you shouldn't need to do this, keep it all in the same table and query your data for before and after the current date...

Still playing, will comment on completion (hopefully), many thanks all

It's good to see in our modern politically correct world that the Yorkie bar now weighs 46g instead of the original 70g and they have removed the 'not for girls' sign from the wrapper.

It was only a joke:D

Many thanks Minty, will take a good look:)

What I was thinking is running another database in the same front-end location say updater.accdb so you could open it from the original, close the original, do the copying, close the updater and load the front end again.

I have a back-end located on a server at z:\database\be.accdb (for example) and users copy the latest version of the front-end to a random location on their local drive. The latest version of the front-end is stored on the server at z:\database\front\fe.accdb and historically users were asked...

Apologies, just trying to see how it worked, no compliment intended ;)

Thank you Minty and the Doc Man, I merely wanted unique order numbers and have no issue with consecutive numbers and missing numbers so creating and saving a number from a primary key at form load time sorts everything perfectly.