Recent content by scopelenz

Hi, thanks for pointing this out to me through a screenshot. I changed the settings accordingly, but it does not change the behaviour of my form fields whichever option I select under 'Behaviour entering field'. When the field is selected for editing, the text in the field disappears whichever...

Hi, I am completely aware where the 'Access Options' button is. However, I am actually asking for the exact option or configuration to change to make the form not behave the way it does now. Does anyone else have any idea?

Hello all, I have posted this question in the Forms sub forum as well, but was directed here to seek better help. I am currently using Access 2007. I have a form that allows users to edit the records which they've entered using the same user account that was assigned. When the user attempts...

Yup. Sorry that I wasn't clear earlier - only the specific text box which I was trying to edit will have its data wiped, and only for that record as well. Where's the options again? I am using Access 2007. Which specific one should I change?

No. The textbox remains fine. I instructed my users to use either Ctrl + Z or the Undo on the ribbon. Allow me to explain again. Some data has been entered in a Form called, Customer Info. The data is captured in text boxes as either text strings or memos. When the data is viewed again...

Sorry for being confusing. Imagine a form with multiple fields, one of which is called "Customer Details". There is a log in page for different users at the start of the database. One of the users has keyed in some information in "Customer Details", and another user - with a separate account...

Existing Data Disappears when attempting to Edit Hello all, I have a rather simple issue. When I open up my form filled with previously entered data, it looks fine, but when I click on it and attempt to append new information in the textbox, the previously entered data disappears and is...

I wanted to do min(pDetailsID) because the aggregate function popped out and I needed something to associate it with pDetailsID. It's not a permanent solution, I figured. So this means I will set up two different queries, one to drag out the pIDs of the first revisions, and another for all...

Hello, I have this rather tricky design which baffles me. The structures relevant to this question are as follows: policy_list: policyID, policyname, region policy_details: pdetailsID, pID (linked to policyID), pnotes, pdate In essence, for every policy introduced, there're several revisions...