Toggle Buttons 1

[jahlmer]

Wow, the wonders of access 97!

I have 6 toggle buttons, and six subforms. So you can visualize this:

The toggle buttons are lined up on the left side of the screen, and there is a big empty space on the right. I have 6 subforms that I would like to come up on the right hand side.

How can this be done?

Thanks for any help.

 

[Maquis]

Hmmmm, put all 6 subforms in the big empty space. If possible, make each subform the same width and height (easier on the eyes when they toggle from one to the other), stack 'em all on top of each other and make all the subforms invisible. (Visible property set to false).

Now on the click event of your option group (Those toggle buttons are in an option group, right?) write some code which will set all the visibles to false and then set the visible property to true of the subform which matches the button pressed.

subform1.visible = false
.
.
.
subform6.visible = false

Select Case me!optgroup1
Case 1: subform1.visible = true
Case 2: subform2.visible = true
etc etc etc
End Select Maq B-)
<insert witty signature here>

 

[jahlmer]

Wow, Maq, thank you! That certainly does work well. I did run into another problem though (go figure). One of my subforms contained a subform, and it didn't like that too much. I'm still so learning and find it humorous that you really end up redoing today what you thought worked yesterday.. I guess one good form deserves another..

Thanks again Maq. I look forward to helping you some time (like you will ever need it!)

 

[Maquis]

LOL, Jahlmer. I need help all the time with Access. There are just sooo many features. Nobody has time to learn them all.

Know anything about getting Access to talk to Groupwise? Maq B-)
<insert witty signature here>

 

[jahlmer]

Unfortunately, no. I've got my 2000 MCSE and know quite a bit (I'm actually a server support engineer for the #2 Computer Manufacturer (#1 in my book, bail out about 20 butts a day), but Access is one of my self-study goals. I know groupwise is a Novell Mail Server like Exchange, yet I don't know much else about it. What are you trying to accomplish? I'll see what I can find.

 

[Maquis]

Well, I really don't have a problem YET. But I'm anticipating one. I'm written a database for a group of users and I've written in a function to e-mail me whenever a user activates a certain feature in the database.

I'm doing this with the docmd.sendobject command, however our company does not use Outlook. We have GroupWise installed as the default e-mail package throughout the company.

Here's where it gets complicated. I have Groupwise, of course, and it is always &quot;on&quot; and sitting in my taskbar. But when Microsoft Access wants to send an e-mail it looks for Microsoft Outlook to send it through. I do have Outlook on my computer since it came installed with the Office suite, but it is not set up to work with our mail server.

When I run the sendobject command it looks around on my hard drive until it finds Outlook and runs the Outlook set up routine in order to force me to use it. %-(

My users don't even have Outlook, so I'm not sure what will happen to them. Since Access doesn't seem to want to use Groupwise I'm afraid it will just crash.

Anyways, if you're still reading this, thanks for listening to me rant and rave. I'll deal with this mess when the database goes into testing and I see what actually happens on their computers. X-) Maq B-)
<insert witty signature here>

 

[Maquis]

Ooops, sorry. Didn't mean to post twice. Clicked the wrong button midway through writing the thing. Maq B-)
<insert witty signature here>

 

[jahlmer]

Yes, that does sound like a go-getter. It would be similar to sending your dog to fetch a stick and not seeing him again. Here are my nitwitty suggestions:

Check the registry settings and perhaps even a crack into a .dll to find the command and what it's looking for (outlook.exe) and find a way to update it on all the computers to find the groupwise .exe and how it sends the message. (that is my not reasonable or likely to happen suggesstion #1 (which could also lead to some disaster recovery)

2. Have have the activation instead log a record in a table and then have it save to or update the table to a file on a printer server with outlook (for instance) and have that program run through the records at time intervals and send them via the command you use for outlook. That way, your email may include the user info in an email that is distributed by one source. Perhaps using the AT command for NT could allow you to accomplish that. Of course, I am oblivious to coding these kinds of things.

Hopefully those paragraphs didnt waste your time to read. I'll keep thinking though (hopelessly).

By the way, which OS are the workstations? And what version of Groupwise?

 

[Maquis]

Hi Jahlmer,

Thanks for the post. Those are good suggestions but unfortunately, I'm a peon in the company. I don't dare try to modify a .dll and I don't have the authority to but anything on the file servers. (Not that I know how anyways).

I'm a programmer, but I'm not a LAN guy. I just stick to application programming and leave the configurations/device drivers/nuts and bolts to someone else.

BTW, the OS is Windows 2000 on my machine and Win95 on the users.

Like I said before, I'm not going to worry too much about it until the users start testing on their machines. Since they don't have any version of Outlook perhaps Access will give up and use GroupWise. I've been reading other posts here and it sounds like others use Groupwise and Access all the time with no problem. (Lucky them)
Maq B-)
<insert witty signature here>

 

[Maquis]

WooHooo!!!! I found this in another thread posted by tlbroadbent.

Modules: Class for sending emails through GroupWise
by Dimitri Furman

http://www.mvps.org/access/modules/mdl0059.htm

Maq B-)
<insert witty signature here>