Limits wrong...
The Long Data Type
2,147,486,647 should read 2,147,483,647
(Open Windows Calculator, select scientific view, and try 2^31 - 1, to get this result. It's a 32-bit signed integer.)
matthewslyman
Last Activity: Feb 9 '20, 02:02 PM
Joined: Nov 30 '06
Location: England
-
...Sifting through Access configuration options...Leave a comment:
-
:-O
I just tested the .mdb in Access 2003 on my Windows XP virtual-PC... I was quite shocked to find that it worked! Who would have guessed that? MS Access 2007 breaks edits on subdatasheets, inexplicably... No wonder you don't like it... As ever, woe betide MS' early adopters...
"The only other thing I noticed was that the records all showed as in record layout, rather than in the design of the sub-form as I expected."...Leave a comment:
-
I presume you've opened the subdatasheets up... Which is the point... As mentioned, it works fine on mine for the main records, but not for the ones in the subdatasheets. Be sure to click on the "plus" signs on the left and try deleting the records in leaf nodes of the tree... Sorry about the stupid instructions if this is obvious to you.Leave a comment:
-
OK. The big anomaly I was talking about was... You try deleting records. It appears to succeed. But then you close the form and reopen it again. And the records are there again. Delete doesn't work on subdatasheet records in Access 2007, on this .mdb or .accdb... I didn't try Access 2003 on this yet.
-->>> Have you tried closing the form and reopening it, and double-checking that the records you deleted do not mysteriously...Leave a comment:
-
I presume you can open the .mdb file (let me know if not.) Just open the .mdb file. Look in the default form. Try selecting a record in a subdatasheet and deleting it, or try selecting multiple records and deleting them. You should start to see anomalies.Leave a comment:
-
... And here's me thinking you'd given up!
;-)Leave a comment:
-
Thought I sent you a .mdb file version... About two mins after you asked for it... It must have gone astray - I'll send it again.Leave a comment:
-
Here's the address of the new discussion on deleting records within recursively nested subforms with self-join relationships on a single table:
http://bytes.com/topic/access/answer...delete-requery...Leave a comment:
-
I've created the stripped-down version, and since you don't want the menu system I've taken that out. So no problems... If you can fix it, you are welcome to document your work (and profit from that documentation) however you see fit, on the RECURSION/ SELF-JOIN side of things anyway...
Re: No customers interested in Access databases... I'm not surprised. I avoid Access data-stores like the plague, especially after the number of...Leave a comment:
-
If you think you can do it, send me your email address... I think there's some way to email people through Bytes... I can see an Inbox link on my profile. Let me know if you can't do that and I'll post my address.Leave a comment:
-
NeoPa, so long as you understand the principles of:- Recursion/ self-join
- Subforms
- The other stuff (e.g. VBA, record locking issues...) that you obviously do understand,
you should be able to understand my code and database relationships. As for the no-entry sign, have you looked at the graphic near the top of this page?
If you will honour my copyright to the menu system, I'll send you a copy so you can see what's...Leave a comment:
-
Thank you, Puppydogbuddy! (Oh my, that's a tongue-twister.) I know what you were suggesting. My delete query actually deletes the correct records, nothing more, nothing less.
NeoPa, I think you're on the right track here... Without the manual DELETE query, when I try to delete PARENT records without first deleting children, despite having cascade-delete selected, I get messages saying:
"Could not update. Currently locked...Leave a comment:
-
I've had the DELETE query running in a DoCmd.RunSQL statement for some time now... There's nothing wrong with it. Except that it puts big fat "Deleted" signs in all the fields, and leaves the deleted record in place (with junk displayed), and messes up the indexing somehow, and prevents Requery from working. The query is technically perfect, apart from that.
I have this code (and some other stuff) inside the Form_Delete...Leave a comment:
-
Naturally, before adding the table twice in the relationships diagram, I amended the indexing/ keys as appropriate. "mode_id" is primary key, "parent_mod e" is INDEXED, with duplicates being acceptable. The relationships diagram shows a one-to-many relationship as it should.Leave a comment:
-
Only one database table is involved - "ui_modes_l kp". I have added it twice to the relationships diagram, with a relationship between "mode_id" on one and "parent_mod e" on the other. I understand that if there is referential integrity WITHOUT cascade deletion, you must first delete the records on the "many" side and then the ones you want to delete on the "one" side (I think this is what you are...Leave a comment:
-
Thank you for your suggestion... Actually I already have "Cascade Delete" switched on, along with all the other Cascade and Referential Integrity options, for that relationship... I have tried without and tried deleting the relationship altogether (relying only on the Form/Subform key relationship as defined in the Form properties box) but to no avail.
It's not the cascade delete that's the problem - since I'm deleting something...Leave a comment:
-
Recursive subforms not cooperating with DELETE/REQUERY...
I have an unusual design and some very unusual issues with my code... I have forced Access to cooperate on everything except one issue - record deletion.
My form design involves a recursively nested form. In other words, the form, m_settings_menu editor_recursiv e has a single subform; m_settings_menu editor_recursiv e (both are viewed as datasheets - so the form is its own subdatasheet.) The Form_Open event modifies the form's recordset... -
OK - I'm going out now... I'll do that later.Leave a comment:
-
Recursive subforms not cooperating with DELETE/REQUERY...
I have an unusual design that Microsoft Access 2003/2007 won't cooperate with... I have forced cooperation on everything except one issue - record deletion.
My form design involves a recursively nested form. In other words, the form, m_settings_menu editor has a subform, m_settings_menu editor. It contains code invoked on the Form_Open event that modifies the...Leave a comment:
No activity results to display
Leave a comment: