Wikipedia:Reference desk/Archives/Computing/2011 June 20

= June 20 =

Help with switchboard (MS Access)
I have read sites, about how to maximize the switchboard when the database is opened , but please will u tell me step by step to : -write the macros in visual basic (it should be docmd.maximize) -enable the macros

but please write it in simple english words...Thank u in advance --95.107.197.91 (talk) 11:31, 20 June 2011 (UTC)


 * Just a note for those who are confused: this is a reference to Microsoft Access scripting. I've edited the title to indicate this. --Mr.98 (talk) 13:45, 20 June 2011 (UTC)


 * The easiest way to do it, in my opinion, is to do the following:
 * 1. Open up the database. Make sure that the Database view is open (so you can see your forms). (You may have to go to Window > Unhide, if it is hidden. If it is hidden to the point where it won't show up in Unhide, or you can't enter Design View as in step 2, close and re-open the database while holding down the Shift key to override any startup options.)
 * 2. Open the Switchboard form. Go to View > Design View to make it editable.
 * 3. Go to View > Properties to open the Properties Window.
 * 4. Make sure that "Form" is selected in the Properties window. Click on the "Event" tab within the Properties window. Scroll down to "On Open" which ought to say "<tt>[Event Procedure]</tt>" in it. Click on the "<tt>[Event Procedure]</tt>" line in "<tt>On Open</tt>," then click on the button with the ellipses (<tt>...</tt>) to the right of it. This will open up the Visual Basic Editor, into a function called "<tt>Form_Open</tt>".
 * 5. Right after the line that says <tt>Private Sub Form_Open(Cancel as Integer)</tt>, add a new line, and type in <tt>DoCmd.Maximize</tt> on that line.
 * 6. Click "Save" in the Visual Basic Editor, and close the Visual Basic Editor. You should be back at your Switchboard form. Click "Save" there. Close the Switchboard form. Re-open it. It should be maximized.
 * Let me know if you have any questions. A shorter version of this would be just to say, "Add <tt>DoCmd.Maximize</tt> to the Switchboard's <tt>Form_Open</tt> function," but I assume that since you asked for a step by step approach, you wanted a more basic explanation, so the instructions above assume very little Access knowledge. You could also do it through Macros, but that would be somewhat more difficult, because the Switchboard already uses VBA scripting, and I'm not sure you can mix-and-match macros and VBA scripting. --Mr.98 (talk) 14:04, 20 June 2011 (UTC)

Thanks a lot 95.107.197.91 (talk) 09:35, 21 June 2011 (UTC)

Memory Stick question
My digital camera stores image files on a little solid state device called "Memory Stick Pro Duo". I used to be able to push that device into a slot on my computer and copy the image files to the hard disk. But that no longer works.

The memory stick still works okay in the camera. When the memory stick is inserted into the slot on the computer, the little green light still comes on to acknowledge the stick is there.

But "Removable Disk (I:)" no longer appears in the Window "My Computer" so I cannot access the files.

I think the memory stick is probably fine since it works in the camera. Is the problem more likely to be with hardware or software?

Thank you, Wanderer57 (talk) 02:02, 21 June 2011 (UTC)
 * I used to do this when t was annoying. What I did was to restart the computer, without the card, and then instert it again. See if it works now, good luck. General Rommel (talk) 02:33, 21 June 2011 (UTC)


 * A Pro Duo usually requires an adapter to fit into a computer's Memory Stick slot. You might also want to check your computer manufacturer's website for a card slot driver so that you can reinstall and/or update the appropriate software.  -- LarryMac  | Talk  17:43, 21 June 2011 (UTC)

how is version control for a development team usually set up?
we have access to virtual servers on request through a cloud sharding solution and I've been tasked with setting servers up for web development (facing the public) of a web application run from the company. From what I can gather, the best practice is to have three servers: production, staging, and development. These would I suppose ideally be three different logical servers (own ip, etc), and even more ideally, as web developers and designers we hopefully wouldn't actually touch production. If I have it right so far, my next question is about version control. I have a recommendation for Gitosis. Shoudl this be set up on the development server, or on a fourth, separate server? Thanks for any other information you would also have. ALSO: at the moment tehre is only one production server, with gitosis half set up for it - it's serving the public. DO you think I can just clone it three times, once for staging, once for development, and on the third clone finish setting up gitosis? Or, what is the best practice approach here? Thanks. — Preceding unsigned comment added by 188.28.194.120 (talk) 23:56, 20 June 2011 (UTC)


 * As for the 3 environments, that's a good approach, and what I'm used to, too, although the middle one is sometimes split into "unit testing" and "integration testing" environments, with programmers doing the unit testing and customers doing the integration testing (also sometimes called beta testing) using cloned production data. StuRat (talk) 08:35, 21 June 2011 (UTC)