Don't know if there is a permission that allows R/W but not delete, but if so, that would be something to try.
I'd recommend a book by Garry Robinson.
Title is "Real World Microsoft Access Database Protection and Security"
Rob
No that's not what I was looking for. I was looking for basing the recordsource for the whole form on a value in a text box or combo box. Its interesting though, that the recordsource for the combo box can reference the form directly (Me.cboComboBoxName), but the code under the recordsource...
Forget the second half of my last post...
I was changing the recordsource after the fact.
When I put in
dam
I only get the exact match (if any) that you would expect.
Rob
I got the answer from another post.
I was not putting anything in the "Input Parameters" property for the form.
Once I did that it worked fine as is.
Thanks.
Rob
Thanks, I tried option 1, above. The missing piece was the "input parameters" property. I wasn't aware of it.
I put in Forms!frmProjects!txtProject
in it and it worked as expected.
Now, here's the weird part. I tried a new sp from scratch. It is:
ALTER PROCEDURE dbo.spProjectsList...
I have developed Access front-ends (forever) for Access backends and also for SQL backends via ODBC. This is my first attempt to work with an ADP. I'm having trouble with the syntax for something that I do often in Access front-ends, i.e., base a form off of a query that references a control box...
I have developed Access front-ends (forever) for Access backends and also for SQL backends via ODBC. This is my first attempt to work with an ADP. I'm having trouble with the syntax for something that I do often in Access front-ends, i.e., base a form off of a query that references a control box...
From my earlier:
You can always brute force it by creating an empty, identical table, and inserting all records (and all fields OTHER THAN THE Autonumber field) ordered by the autonumber.
That will resequence.
Rob
I agree with PHV, but I do use the autonumber as a means of only determining order of input, no real meaning. In which case, it doesn't matter that there are big gaps.
However, to answer to your question.
It looks as if you ran some insert queries that failed and were "rolled back." When this...
Yes, you can do it, but can get quite painful.
What I have done in the past is create a query for each table that translates old (bad format) names into new (good format) names. Then reference only the queries in my new code/forms/queries.
In query designer for field 'due date' just put in...
Essentially, yes.
But you CAN set the permissions separately, if you want.
For instance, if you permissions for a group on a table (link) in the front-end to Administer and set the permissions on the table itself (in the backe-end) to Read-only, then anyone from that group accessing through the...
What I do when I split a secured database is essentially copy it (via the file system), calling one MyApp.mdb and the other MyData.mdb.
Open the Mydata.mdb (while logged into your secured workgroup) and delete all forms/reports/queries/(most) modules.
Open the Myapp.mdb and blow away the...
If you HAVE to share a front-end (I ran across this too, and had to share some temporary tables). I just added a username column to each table and most of my stuff worked with minor modifications. I just filtered on the username.
However, I have HEARD that even with Citrix it MAY BE better...
To make a long story short, you CAN easily take care of the insertion for yourself.
In the before-update event of the subform just do something like:
Me.YourForeignKeyField = Me.Parent.PrimaryKeyOnMainform
HTH.
Rob
Did you check the Link Master and Link Child properties of the subform control (not the subform itself)(check under the 'data' tab).
WHen there is a proper Primary key foreign key relationship defined between the 2 tables Access automatically provides the field names. If the foreign key on the...
WHat happens if you open the form, then assign the picture, like below??
Dim file As String
file = "C:\Documents and Settings\auheatw1\my Documents\RCFA SP\Pictures\" & Me!Picture1
DoCmd.OpenForm "frmLargePicture
Forms![frmLargePicture]!picture.Properties("Picture") = file
You mean when you add data to the subform, you are actually getting a new record in the mainform?
Is your subform based on a query that involves the Mainform's table.
That could be your problem.
If your subform contains a query/table that only includes the one table from the Many side of the...
It MAY not be the ADO that's biting you. Are you running an Access front-end that went from 95 to Access 2000?
I had a HUGE performance hit when I upgraded from 97 to 2000 and it was due to the now infamous "Track autocorrect" option under Tools/Options/General. This option is ON by default...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.