Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.
Course Of The Month
10 days, 1 hour left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
send OleObject to back
Posted on 2011-03-10
hi experts,
Here's my problem: I'm trying to monitor RFC's in combination with a visio workflow diagram.
For this purpose I created an access-database with RFC's.
On a single form (of a rfc) there is a OleObject which is linked to the workflow diagram.
Over this diagram several buttons are placed. One specific button changes the status of the RFC.
OleObject Properties:
Source Doc is the vsd document
class=Visio.Drawing
When the form opens I use
Me.OLEvisioDocument.Action
(if I don't the drawing doesn't show)
but if the form is opened, it shows the visio drawing with BUTTONS BEHIND THE DRAWING.
How can I get the buttons to the front using vba?
Or is there another way to solve this problem
Here's my problem: I'm trying to monitor RFC's in combination with a visio workflow diagram.
For this purpose I created an access-database with RFC's.
On a single form (of a rfc) there is a OleObject which is linked to the workflow diagram.
Over this diagram several buttons are placed. One specific button changes the status of the RFC.
OleObject Properties:
Source Doc is the vsd document
class=Visio.Drawing
When the form opens I use
Me.OLEvisioDocument.Action
(if I don't the drawing doesn't show)
but if the form is opened, it shows the visio drawing with BUTTONS BEHIND THE DRAWING.
How can I get the buttons to the front using vba?
Or is there another way to solve this problem
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2
2
5 Comments
Active today
Do you need to toggle the buttons to show at times, but at other times to NOT show?
If so, then considering that you're using OLE methods, I'd suggest you use a Tab control. Place your OLE container on one page, and your buttons on another, then show/hide the tab pages as needed. Tab pages are given an "index", and you use that to toggle the page. For example, if I have a Tab control named tbMyTab, I'd do this:
tbMyTab = 0 '/shows the first page
tbMyTab = 1 '/shows the second page
OLE containers can do some strange things in Access, so it's best to isolate them in cases like this.
==========================
If not, and if you're looking to "float" the buttons over the OLE container, then I'd suggest you consider other options, like moving the buttons to the top/bottom/side of the OLE container perhaps.
If so, then considering that you're using OLE methods, I'd suggest you use a Tab control. Place your OLE container on one page, and your buttons on another, then show/hide the tab pages as needed. Tab pages are given an "index", and you use that to toggle the page. For example, if I have a Tab control named tbMyTab, I'd do this:
tbMyTab = 0 '/shows the first page
tbMyTab = 1 '/shows the second page
OLE containers can do some strange things in Access, so it's best to isolate them in cases like this.
==========================
If not, and if you're looking to "float" the buttons over the OLE container, then I'd suggest you consider other options, like moving the buttons to the top/bottom/side of the OLE container perhaps.
You did not state what version of Access you are using.
Certain types of controls, in certain situations, simply cannot be made to do this.
Keeping this in mind...
A test would be something like this:
Open the form in design View
Select the buttons (Making sure you do not select the OLE object) and use the "Bring to Front" option.
(Or conversely, Select the button and chose "Send to Back")
Just curious, ...
Why not simply put the buttons "beneath" the OLE object, and avoid the issue altogether?
JeffCoachman
Certain types of controls, in certain situations, simply cannot be made to do this.
Keeping this in mind...
A test would be something like this:
Open the form in design View
Select the buttons (Making sure you do not select the OLE object) and use the "Bring to Front" option.
(Or conversely, Select the button and chose "Send to Back")
Just curious, ...
Why not simply put the buttons "beneath" the OLE object, and avoid the issue altogether?
JeffCoachman
sorry my reaction took so long
LSMconsulting: i want to see the diagram and the buttons at the same time
boaq2000: access 2007: Bring to FRONT/BACK: is this possible in vba??
I also use a tggle button in the form heading. If i change the value the diagram the buttons appear in front of the daigram. But not just on opening the form.
LSMconsulting: i want to see the diagram and the buttons at the same time
boaq2000: access 2007: Bring to FRONT/BACK: is this possible in vba??
I also use a tggle button in the form heading. If i change the value the diagram the buttons appear in front of the daigram. But not just on opening the form.
Active today
BringToFront is an option on the rightclick menu. Select the Control, right click and you'll see it in the popup menu (in design view).
As Jeff said: Put the buttons below or to the side. OLE Objects are quirky (at best) in Access, and you'll never get a reliable process out of this.
As Jeff said: Put the buttons below or to the side. OLE Objects are quirky (at best) in Access, and you'll never get a reliable process out of this.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
This article describes two methods for creating a combo box that can be used to add new items to the row source -- one for simple lookup tables, and one for a more complex row source where the new item needs data for several fields.
Code that checks the QuickBooks schema table for non-updateable fields and then disables those controls on a form so users don't try to update them.
Familiarize people with the process of retrieving data from SQL Server using an Access pass-thru query. Microsoft Access is a very powerful client/server development tool. One of the ways that you can retrieve data from a SQL Server is by using a pa…
Using Microsoft Access, learn some simple rules for how to construct tables in a relational database.
Split up all multi-value fields into single values:
Split up fields that belong to other things into separate tables:
Make sure that all record…
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month10 days, 1 hour left to enroll
623 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.