home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.ms-windows.apps:7342 comp.os.ms-windows.misc:6407
- Path: sparky!uunet!spool.mu.edu!enterpoop.mit.edu!eru.mt.luth.se!lunic!sunic!isgate!krafla!gummi
- From: gummi@rhi.hi.is (Gudmundur Bjarni Josepsson)
- Newsgroups: comp.os.ms-windows.apps,comp.os.ms-windows.misc
- Subject: Access: bug or stupidity?
- Keywords: access, bug
- Message-ID: <5979@krafla.rhi.hi.is>
- Date: 21 Jan 93 10:18:50 GMT
- Sender: usenet@rhi.hi.is
- Followup-To: comp.os.ms-windows.apps
- Lines: 32
- Nntp-Posting-Host: hengill.rhi.hi.is
-
-
- I'm curious to know if this is a bug in MS Access or my own stupidity.
-
- I've created a form which cointains a subform. Both of those are based
- on fairly simple queries. Everything was working fine until:
-
- I brought up the subform in design mode
- Brought up the properties window
- Added a macro to the Before update property field
- Added a macro to the After update property field
- Closed the form and saved
-
- After I'd done this the subform became read-only. I checked the
- editing fields in the properties list and they were correctly set. I
- tried to remove the macros, delete and re-create the subform, repair
- the database, exit Access, exit Access and Windows, exit Access and
- Windows and reboot the machine. No good. The form is always
- read-only.
-
- ? ? ?
- ?_ ?
- / \
- C-O-O-D
- | | |
- |\_/|
- \_/
-
-
- Gudmundur Bjarni Josepsson
- Computing Services
- University of Iceland
- gummi@rhi.hi.is
-