Huffman, Jarad B.
jbhuffman at mdh.org
Fri May 30 09:00:39 CDT 2003
No worries, I thought I had heard that somewhere. -----Original Message----- From: Wortz, Charles [mailto:CWortz at tea.state.tx.us] Sent: Friday, May 30, 2003 8:50 AM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Command Line WRKGRP switch - revisited Jarad, I am not saying your way is wrong, just that the way I do it has never failed me. I cannot recall where I read it, but some knowledgeable person said to do it in this order: first the path to the proper version of MSAccess.exe, second the /wrkgrp switch, third the path to the proper .mdw file to use, fourth the Access application to open. Since I started to use this order on all my shortcuts I have not had any problem with shortcuts through several versions of Access. Charles Wortz Software Development Division Texas Education Agency 1701 N. Congress Ave Austin, TX 78701-1494 512-463-9493 CWortz at tea.state.tx.us -----Original Message----- From: Huffman, Jarad B. [mailto:jbhuffman at mdh.org] Sent: Friday 2003 May 30 08:30 To: 'accessd at databaseadvisors.com' Subject: RE: [AccessD] Command Line WRKGRP switch - revisited I believe the /wrkgrp switch and parameter have to be at the end of the command line. If you have it before your mdb filepath, it might cause some trouble. Jarad Huffman -----Original Message----- From: Porter, Mark [mailto:MPorter at acsalaska.com] Sent: Thursday, May 29, 2003 5:47 PM To: 'accessd at databaseadvisors.com' Subject: RE: [AccessD] Command Line WRKGRP switch - revisited Good point, I've noticed the 'fixit' behavior with WinXP pro shortcuts also. But this shortcut was built on the machine itself (WinXP with a UNC workgroup filepath, double-quotes around each filepath like "<msaccess.exe>" /wrkgrp "<.mdw with UNC pathing>" ".mdb file path") I've also cleared the 'Start In' box to avoid it starting in the wrong place. I'm stumped. Mark -----Original Message----- From: Drew Wutka [mailto:DWUTKA at marlow.com] Sent: Thursday, May 29, 2003 2:43 PM To: 'accessd at databaseadvisors.com' Subject: RE: [AccessD] Command Line WRKGRP switch - revisited Um, complete shot in the dark, but since W2k, Shortcuts have more internal information then you think. For instance, if you have a shortcut pointing to something.exe on your root C: drive. Then one day you move that .exe to another drive or folder, W2k and up will actually 'fix' your shortcut for you. (It's a service, so it may be turned off or on, it can even be setup to be LAN wide). One bad effect that myself and my co-network admin has noticed, is that you can have problems trying to copy a network shortcut from one machine to the next, because the shortcut is actually a shortcut to a internal reference on your local machine, that points to the network resource, so copying the shortcut elsewhere is giving them a shortcut to your local internal reference/shortcut, which they may not be able to access, in fact, it will usually try to access the same file/folder location on your local machine. To fix this, we just made new shortcuts from scratch. Drew -----Original Message----- From: Porter, Mark [mailto:MPorter at acsalaska.com] Sent: Thursday, May 29, 2003 5:12 PM To: 'accessd at databaseadvisors.com' Subject: RE: [AccessD] Command Line WRKGRP switch - revisited Thanks for the responses, which fixed a lot of the issue. However, on a WinXP Pro machine I'm getting an error on the /wrkgrp switch. it is looking for the *.mdw filepath by starting in the local documents and settings, instead of using the UNC path. Has anyone seen/fixed this behavior? Thanks, Mark -----Original Message----- From: Porter, Mark [mailto:MPorter at acsalaska.com] Sent: Wednesday, May 28, 2003 10:11 AM To: 'accessd at databaseadvisors.com' Subject: RE: [AccessD] Command Line WRKGRP switch After the responses all had the msaccess.exe executible path I recalled that it was required with the other times that I've implemented it. I never did know why though. Thanks for clearing it up. Mark -----Original Message----- From: Charlotte Foust [mailto:cfoust at infostatsystems.com] Sent: Wednesday, May 28, 2003 9:59 AM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Command Line WRKGRP switch Charles answered your question, but the reason it isn't working is because *all* command line arguments are ignored if you do not include the full path and filename to the Access executable in your shortcut. Since /WRKGRP is a command line argument, it gets ignored when you only include the database path and the workgroup and leave out the Access executable. Charlotte Foust -----Original Message----- From: Porter, Mark [mailto:MPorter at acsalaska.com] Sent: Tuesday, May 27, 2003 4:39 PM To: 'accessd at databaseadvisors.com' Subject: [AccessD] Command Line WRKGRP switch I have a secured Access 2000 file format database and want to use the /wrkgrp command line switch in a shortcut to associate with the workgroup on startup. This command switch is not working ( F:\sis\CCA_App.mdb /WRKGRP "F:\sis\CCA_Workgroup.mdw" ) the user accesses the correct file but under the system.mdw workgroup. I've verified that the file locations and the spelling are all correct. Any ideas? Thanks, Mark _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com