Search results

Table fields don't like mixed data. So, I reckon you've probably got that particular field set for Numbers, hence text cannot be imported. If you changed the field to Text then, probably, all the data will be accepted (numbers will look like numbers but be stored as text). The proper answer...

Try the attached ... it's a feature I have used before. It's simple (maybe too simple) but effective enough perhaps for what you want to achieve ... logs each User into Logged_Users table on entry and deletes them on Exit via the Main Menu. It's easy enough from there to build a form, query...

I would just trawl Google for a JPG or BMP of the image you require and store it in a table in the appropriate record as Data Type "OLE Object" Table would look something like, e.g. Value "1" = "JPG_1" Value "2" = "JPG_2" Value "3" = "JPG_3" I have in the past used this technique to bring...

You could perhaps also consider hiding all the tables in the BE file, just in case users still manage to find a way of loading it.

Interesting! Suggest first of all you add an additional Field to each record in your table, being MONTH e.g. 2010_10 Then, once you've cleared down the data, you need to run a crosstab query using MONTH as the Column Header (descending order) and showing USERS with a current month...

How would they even know there's a split database, and where to find the _BE file? Unless you've told them? You should perhaps, in any case:- 1) Disable the Database Window at Startup 2) make sure the FE is menu/form driven 3) Hide the Table objects 4) Even better perhaps, issue the Database...

Yes, by recognising each user's LAN ID within relevant open Forms you can then enable/disable command buttons by reference to the LAN ID the expression you need to use to trap the LAN ID is, I believe:- =Environ$("USERNAME") The 'Permissions' table, which you can query against, can be as...

Is all this code placed in the On Current form property? I tried this and got an error message when the code Private Sub Form_Timer() was read ... given that it follows an "End Sub" command is this the start of some additional code? Also, what does "Restore" link to? I'm very close ... but...

Does your "F_restore" form have any fields on it or is it completely blank??

I would now like to road-test the RESTORE code ... but it looks like there's a form "F_Restore" that needs to be built, into which I'm guessing the Restore coding needs to be copied into the On-Timer event property?

The code fails for me at this point also, error message received is "Run-time error 76: Path not found! At this point the code has correctly created the \Backups\2011-09-28 folder but this error seems to stop any files being copied into the folder? Any ideas why? Update: I changed source =...

OK ... I'll copy the code and see how I get on ... many thanks

Thanks ... I'll try this out asap

Does the above Backup script require any modification to handle a single BACKEND file requiring daily backup? e.g. C:\Program\backend_be.mdb backed up as C:\Program\Backups\backend_be 20110927.mdb Many thanks!

Agree totally about picture file size and resolution as even a single large image can cause Access a seizure! What's the best technique to store the images and index/render them back to the database?

Sounds like a normal project to me lol ... I think, firstly, you need to determine what Tables you need to create. Once you populate the Tables with data you can then build the Queries and create/link Reports to the Queries.

In simplistic terms this sounds achieveable ... creating variable Queries based on multi-Table data with the subsequent output being converted to Word or even PDF output.

The first element of your requirement is tricky but manageable ... I have seen threads relating to this very requirement on this site but it's not my expertise, sorry. However, even with this solution you need to be efficient and consistent with how you manage your photos i.e. keep them under a...

Create a Header table containing the details of the claim, including a field called "Claim Number" Create a second table with two fields ("Claim Number"; "Picture") holding separate records for each JPG Link the table in a query via the common field i.e. "Claim Number" This should then...

Yes ... install the Front End file plus Access Runtime 2007 (free download) on the workstation, whilst the Backend file remains on the Server. The Linked Table Manager features will all still work.