Avoiding #Deleted (1 Viewer)

CedarTree

Registered User.
Local time
Yesterday, 22:38
Joined
Mar 2, 2018
Messages
404
Hello,

Have a main form with two subforms.

First datasheet subform lets me select the record I want to look at. On Current, I then dymically load the data from sqlserver into the 2nd subform. For example, subform1 lets me choose which baseball team I want, and subform2 shows me statistics on that team.

When loading the underlying data for subform2, I temporarily see "#deleted". I get it... the data isn't there for a moment. But can I temporarily hide the #deleted? I've tried turning application.echo off, etc. Any other tricks? Maybe hide the subform while data loads?
 

isladogs

MVP / VIP
Local time
Today, 02:38
Joined
Jan 14, 2017
Messages
18,186
Not quite clear why the data isn't there immediately.
Is the subform record source only added after you make the first selection?

Anyway perhaps hide subform2 until the data has been loaded?
 

theDBguy

I’m here to help
Staff member
Local time
Yesterday, 19:38
Joined
Oct 29, 2018
Messages
21,358
Hi. You didn't specify how you're "loading" the data, but maybe you could try "unloading" it from subform 2 first before reloading it again. Just a thought...
 

CedarTree

Registered User.
Local time
Yesterday, 22:38
Joined
Mar 2, 2018
Messages
404
I think hiding the subform works. Thanks.
 

AccessBlaster

Registered User.
Local time
Yesterday, 19:38
Joined
May 22, 2010
Messages
5,828
After the delete operation, can't you requery or refresh the underlying record source for that subform2 ? Just speculating.
 

missinglinq

AWF VIP
Local time
Yesterday, 22:38
Joined
Jun 20, 2003
Messages
6,423
...After the delete operation, can't you requery or refresh the underlying record source for that subform2 ?

Actually...the OP says nothing about Deleting a Record!

Does #Deleted really show if data is simply 'unavailable?'

Or is this a sign of corruption?

Linq ;0)>
 

AccessBlaster

Registered User.
Local time
Yesterday, 19:38
Joined
May 22, 2010
Messages
5,828
Actually...the OP says nothing about Deleting a Record!

Does #Deleted really show if data is simply 'unavailable?'

Or is this a sign of corruption?

Linq ;0)>
Good point. But hiding corruption cannot be the answer either.
 

missinglinq

AWF VIP
Local time
Yesterday, 22:38
Joined
Jun 20, 2003
Messages
6,423
I agree, of course! Preventing an error, rather than covering it up, is always, well at least always, the way to go!

I just wondered if anyone knew of any other reason for #Deleted to show except when a Record had actually been deleted.

Linq ;0)>
 

Users who are viewing this thread

Top Bottom