By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,600 Members | 1,683 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,600 IT Pros & Developers. It's quick & easy.

Problems making or deleting records through a form control button

P: n/a
uv
Hi!
I'm having problems submitting a new record through the form.
I'm working with the wizard and I've added a control button to my form
for entering entering a new record but for some reason it only works
for the first record I enter.
The same goes for deleting a record.
It says I can't access the records, and that goes for both making or
deleting.
I'd appreciate your help very much,
uv
Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
er******@tau.ac.il (uv) wrote in message news:<23**************************@posting.google. com>...
Hi!
I'm having problems submitting a new record through the form.
I'm working with the wizard and I've added a control button to my form
for entering entering a new record but for some reason it only works
for the first record I enter.
The same goes for deleting a record.
It says I can't access the records, and that goes for both making or
deleting.
I'd appreciate your help very much,
uv


Stupid question, but what happens when you create a form using a
wizard and don't modify your form at all? Can you enter records?
What's the code behind your button?

If you can't delete records... do you have AllowDeletions property of
your form set to Yes?
Nov 13 '05 #2

P: n/a
Hi Pieter,
Thanks for the reply!
I already figured it out:
What happened was I had the nime of an entity ("organism") drawn out to
a diffent table than the organism itself, bound by the id field in a
1to1 relationship.
The autonumber of the id was in the organism but none of the obligatory
fields to fill were in that table but in the name and other tables.
This caused problems as not always an organism field was created.
My current solution is to reunify both tables but I should probably
learn some SQL so I can tie them more elegantly by an event.
Or is there another way out?
Thanks alot,
uv

*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.