[dba-SQLServer] SPAM: Re: Continuous Form Record Disappears

[David Emerson]

Further to below, I have 7 screens that are set up similarly using
Me.UniqueTable etc.  2 of them show the problem, the other 5 work without a
problem.  I have not been able to find what the difference is between them
:(

If there is only 1 record showing on the screen (ie all the other records
have been scrolled up so only the last record is showing) then the previous
record doesn't blank out.  But if more than 1 record is showing on the
screen then the last record blanks out when a new record is started.

Clicking in the blank fields will make the data in that field appear.

-----Original Message-----
From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On
Behalf Of David Emerson
Sent: Wednesday, 22 May 2019 2:53 p.m.
To: 'Discussion concerning MS SQL Server'
Subject: Re: [dba-SQLServer] SPAM: Re: Continuous Form Record Disappears

Thanks for the response Jim,

This is the first time I have seen it happen.  I have a number of other
databases that have worked exactly the same way for over 5 years without
ever seeing this problem.  

I hope it is not some "feature" of Office 365 - the client is running it on
that and I am using Access 2010.

David

-----Original Message-----
From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On
Behalf Of Jim Lawrence
Sent: Wednesday, 22 May 2019 2:16 p.m.
To: Discussion concerning MS SQL Server
Subject: SPAM: Re: [dba-SQLServer] Continuous Form Record Disappears

When I was printing, in a network situations, I use to create a empty
recordset, matching the report, populated it via a query or code and then
used that isolated recordset. It would always work perfectly even if the
network blew up.

I think pulling directly from a live database can cause problems when
multiple users are using the same data.
 
Jim

----- Original Message -----
From: "David Emerson" <newsgrps at dalyn.co.nz>
To: "Discussion concerning MS SQL Server"
<dba-SQLServer at databaseadvisors.com>
Sent: Tuesday, May 21, 2019 6:56:17 PM
Subject: [dba-SQLServer] Continuous Form Record Disappears

Hi Listers,

 

I have an Access 2010 accdb using SQL 2017 as the back end.  I have a
continuous form which has the recordset assigned as below when the screen is
opened.

 

    Set rstTemp = basRunDataObject("dbo.usp_RWfrmRework " & Nz(Me!cboFilter,
0) & "," & lngTeamSubID & "," & lngTeamID, adCmdText)

    Set Me.Recordset = rstTemp

    Me.UniqueTable = "dbo.RWRework"

    Me.ResyncCommand = "SELECT dbo.RWRework.* FROM dbo.RWRework INNER JOIN
dbo.RWTeamMember ON dbo.RWRework.RWTeamMemberIDNo =
dbo.RWTeamMember.RWTeamMemberID INNER JOIN dbo.RWTeamSub ON
dbo.RWTeamMember.RWTeamSubIDNo = dbo.RWTeamSub.RWTeamSubID WHERE
dbo.RWRework.RWReworkID = ?"

    Me.Requery

 

This works fine, records can be added and edited.  The only problem is that
when a new record is inserted (by entering in something in any field) then
the previous record fields show blank as if there was no data in them.  The
data is still there.  When the new record is saved and another record is
inserted then the data from the previously blank looking record appears and
the data from the last record entered is not blank looking.

 

Has anyone come across this before or have any ideas how I can prevent it?

 

Regards

David Emerson
Dalyn Software Ltd
Wellington, New Zealand

 

 

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com