Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 483
  • Last Modified:

Bookmark form before Design then Open to same record

Experts,

I have a form.
I Design the form.
I do stuff.
Then open again.

I need the form to open to the same record [ID] I was on before I Designed the form.  I am sure this has something to do with Bookmark but I dont know what events to use  under this particular type of scenario.  

thank you
0
pdvsa
Asked:
pdvsa
  • 7
  • 4
  • 3
  • +1
1 Solution
 
Rey Obrero (Capricorn1)Commented:
you can only do that by filtering the record source of your form using the record ID you are working on.

if you are working on record id 1
use a query like this as record source of your form

select * from tableName where recordID=1

after your design work is done, replace the record source of the form


you can also store the record ID to a table and use it to filter the record source of the form
0
 
pdvsaProject financeAuthor Commented:
OK how would I make the recordID more dynamic?  I probably dont understand completely but what I mean is the select * is hard coded to recordID = 1 and I can be on 1 of thousands of record ID's.  

I thought using bookmark and that     Dim vID and vID = Me.ID code you gave me yesterday or some kind of combination would be the solution or maybe a tempvar.  I do open the  form using tempvar but delete the tempvar after opening.
0
 
Rey Obrero (Capricorn1)Commented:
ok.. try this

private sub form_current()

tempvars.add "myID", me.ID.value


end sub

private sub form_load()

if not isnull(tempvars!myID) then

with me.recordsetclone
      .findfirst "[ID]=" & tempvars!myID
      if not .nomatch then
            me.bookmark =.bookmark
      end if
end with

end if

end sub
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
PatHartmanCommented:
Bookmarks change each time a query runs.  Only the Unique ID of the record is a permanent identifier.  Since you are going into design view (I'm not even going to ask but I will tell you this is poor practice and will not work if you need to distribute using the runtime engine), the query needs to run again when the form reopens.  That means a new set of bookmarks.  So, save the ID in a Tempvar or in a table if you need it to persist longer.
0
 
pdvsaProject financeAuthor Commented:
Pat:  using bookmarks is poor practice?  

I have code in On Load right now (as a macro).  I converted to code and am encountering an error.  About to post it in a separate question.
0
 
PatHartmanCommented:
It is not that using bookmarks is poor practice.  They simply won't work from one recordset to another so you will need some other place to save the record ID (not the bookmark).  Bookmarks are regenerated each time a recordset is opened.  

The poor practice is putting an object into design view to make changes to it on the fly.
0
 
pdvsaProject financeAuthor Commented:
How else could changes be made to an object if not through design mode?
0
 
pdvsaProject financeAuthor Commented:
Or do you mean go to the object on the left (db window)?
0
 
Rey Obrero (Capricorn1)Commented:
@pdvsa

did you test the codes i posted?
0
 
pdvsaProject financeAuthor Commented:
Cap:  actually not yet...only because I currently have on Load event there and as a macro and conerted to code and get the error... I see u posted a response.  I will be at computer after a bit.

Not at computer at moment.  Thank you (sent from phone)
0
 
Rey Obrero (Capricorn1)Commented:
you know that after the testing period, you have to removed those codes, right?
0
 
pdvsaProject financeAuthor Commented:
"I see you posted a response". I meant on my other question posted a few min ago.
0
 
PatHartmanCommented:
Why do you need to make design changes when the user is interacting with the app?  Design changes should be made in design view by YOU.  Users should simply be using the app to work with data.
0
 
mbizupCommented:
Backing up Pat's comment here --  Doing runtime design changes through code might be a good academic exercise, but it is a bad idea in a production database for a variety of reasons.  The reason that always jumps to mind is that code like that WILL fail if you ever need to distribute your database in accde/mde format to users in a runtime environment.

That said, I'm not sure that you both are thinking on the same plane.

<<
I have a form.
I Design the form.
I do stuff.
Then open again.
>>

Are you doing these design changes manually, or are you automating them with code?

EDIT:

Just to be clear, I'm not looking for points in this thread -- just trying to clear up what I think might be a misunderstanding (either between you and Pat or completely on my part)
0
 
pdvsaProject financeAuthor Commented:
Excellent.   That worked.  I deleted the previous codes and am now using yours On Load event.
0

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

  • 7
  • 4
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now