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

Please, any help appreciated

P: n/a
I have an access 2k3 front end linked to a SQL Server 2k backend and
have been having quite the issue with deleting.. I have a form with a
subform, in datasheet view.. there are 2 combo boxes both of which are
master links to the sub datasheet, now when I select a plant and a
date, it brings up all the correct records, but my problem is, if i try

deleting a row from the datasheet it deletes it. but then adds the
topmost record from my table in the database and changes the date to be

the same as the rest in the datasheet. This _seems_ to only happen if I

delete a row at the bottom of my datasheet. Any insight into why this
is happening is greatly appreciated, thanks!

Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Beacher wrote:
I have an access 2k3 front end linked to a SQL Server 2k backend and
have been having quite the issue with deleting.. I have a form with a
subform, in datasheet view.. there are 2 combo boxes both of which are
master links to the sub datasheet, now when I select a plant and a
date, it brings up all the correct records, but my problem is, if i
try

deleting a row from the datasheet it deletes it. but then adds the
topmost record from my table in the database and changes the date to
be

the same as the rest in the datasheet. This _seems_ to only happen if
I

delete a row at the bottom of my datasheet. Any insight into why this
is happening is greatly appreciated, thanks!


For the functionality you want neither your main form nor the ComboBoxes
should be bound, but they currently are. While you are changing the
ComboBoxes only with the intent to control which records are displayed in
the subform since the controls and main form are bound you are actually
editing the first record that the main form is bound to.

Despite what the MasterLink / ChildLink wizard might have indicated it is
not required that the main form be bound in order to set those properties
up. That is only a requirement of the wizard.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.