I created a Workgroup file (Project.mdw), assigned different Permissions to different Groups, and put different Users in appropriate Groups.
The above setup is working fine and just as required. But, if I remove or rename the Workgroup file, MS Access does not look for it, creates in its own Workgroup file and starts just as usual - without asking for the Password, or caring about the Permissions and/or restrictions set.
How can I make the database file bound to the MDW file, so that it does not open without it.
I created a Workgroup file (Project.mdw), assigned different Permissions to different Groups, and put different Users in appropriate Groups. The above setup is working fine and just as required. But, if I remove or rename the Workgroup file, MS Access does not look for it, creates in its own Workgroup file and starts just as usual - without asking for the Password, or caring about the Permissions and/or restrictions set. How can I make the database file bound to the MDW file, so that it does not open without it.
I am looking for a little help getting a database created in access 2000 to open in access 2003. The creater of the database put security on it and I have the security doc. However, I do not know how to give permission to open the database in 2003.
Ok.. I have done this before at another job, but this network (or stupid me) is giving me trouble. I'm trying to setup a database security (login/password) for a database on a network. I setup the security levels..setup a seperate workgroup... From my computer it logins fine with the correct workgroup.
All.. I have an access 2003 application I have front end and back end separately. When I click "Make MDE File" from tools menu, nothing happens. When checked the Windows Task manager(Windows 2000), CPU usage is 100% and MS ACCESS is not responding. There are no messages.
I have a dbf file that I need to somehow get the table data out of, and into access, excel, or some other usable format. I searches the MS Knowledge Base and read several articles on updating the Jet 4.0 drivers (up to date) and updating Foxpro ODBC drivers, etc. I also searched these forums, and I have yet to find any solution that works.
I think this dbf file might be Foxpro, but I'm not sure. I don't know anything about Foxpro. I was getting an error message "unexpected error from external database driver (8961)", until I read an MS article stating that I should change the name of the Borland folder to BorlandOld and try re-importing. Now Access 2003 just says: "external table not in the specified format".
hello good afternoon. i am trying to open different file types using ms access. the following piece of code i found would only open 'word' documents. how do i make this piece of code more flexible to open pdf documents and excel as well. as it is currently i have a txt field on my form and if the path in the txt fiels leads to a word document when i click a button the word file opens. i want it to open a pdf or excel doc if it was in the txt field
[code] Sub OpenWordDoc(strDocName As String) Dim objApp As Object
'Opens the document
Set objApp = CreateObject("Word.Application") objApp.Visible = True objApp.Documents.Open strDocName
We have an old Access 97 database with a workgroup file. The problem was that the machine was upgraded and the software was changed to XP. They support guys moved all files to the new PC except the the workgroup file. We can't fine a backup of the w/g file.
I am unable to upgrade the database to access 2002 because of the permissions.
What is the easiest way to get past this stumble block.
Present Go to user computer, and then manually to join the workgroup.
Is this possible?
Send email to new user. Join workgroup using a zip file. When file is un-zip the user automatically joins the workgroup and places a short cut on there desktop.
This is more of a point of interest then a question, at work, Access defaults to a central workgroup file, so all Access files opened on a work machine will prompt for a user name and password, and only let you in if you get it right... but if you move the work group file, even after it has been open using that workgroup file, it will just let you straight in and GIVE YOU ADMIN RIGHTS!
No one really seems to know about this... does it happen if you manually set the workgroup file? Or is this just a security hole if you rely on the default? I'm not sure yet, haven't tested, but i fell people should be made aware (happens for sure on Access2002, haven't tested it on any others)
I want to import a fixed length file into access 2003, it can only be imported directly into access 97/2000. This site, link http://www.ams.usda.gov/science/pdp/03data.txt has the idea, but the problem is I can find the "2003 Data zip file" which this site is refering to. - I have looked for it on the ms office 2003 cd,but I still can find it. Please can someone tell me where I can find de "2003 Data zip file"?
I've set up security on my database before with great success, and now I'd like to use the same workgroup file (a copy with a new name and location) to secure a nes db.
I open the new db, and join my earlier created mdw file. I'm prompted with that I have joined my workgroupfile.
I then set permissions for each user in the workgroupfile, remove admin rights for the admin user account, and assign admin rights to my own account. I am also the owner of thr db.
I now run the security wizard, and I make no changes to any checkboxes.
This goes nicely, and the wizard closes after making a backup file.
I now want to re-join the system.mdw file, so I don't get prompted with the logon dialog when opening a new db or an unsecured db.
If I now try to start my new secured db by double-clicking on the secured mdb file it opens ?????
I am trying to setup User Level Security around a Purchase Order Database that I created. Using the Wizard I was able to setup different users with different permissions.
However, as I found out the hard way (but I did recover it), 'joining' a PC to a my new security workgroup forces all Access databases on the PC to use this.
Is there a way to force just this one Access .mdb file to use the newly created PO Workgroup security file ?
I am aware of setting up a shortcut to point to thesecured db. Ie: "C:Program FilesMicrosoft OfficeOfficemsaccess.exe" /wrkgrp "C:PO FormsMyWorkgroupFile.mdw" "C:PO FormsMyDB.mdb" /user
But despite the above shortcut, couldn't users just find out where it points to (by looking at the Properties of the shortcut), and open the .mdb file based on that ?
I recently created a workgroup for an access database and it works fine. But I have other versions of that same database (beta copies) for which I didn't create that workgroup file. They have different names than the first DB for which I made the workgroup. But even when I open those beta copies it still launches the workgroup file (system.mdw) and prompts me to login. What do I need to do to revert these changes and go back to the unsecured version of my database?
First of all, I'd like to thank everyone who's a member and has helped someone at some point within the forums! I'm quite new to Access and have received a massive amount of help on one of my first databases.:)
As the title points out, I'm not sure about the WIF. If I have two database in the same location, lets say their called DB1 and DB2 and I create a WIF for DB1, this wont affect DB2, will it? For example, it wouldn't create security for DB2?
Another senario is, if I have two databases nameed DB1 (basically one is a copy) within lets say two different subfolders within the same top level folder, because they are the same name, would this mean that they would both be affected by the same WIF?
I recently created a WIF like this and had to enter a password for both databases! to my consternation, I deleted the DB (along with the WIF) with which I made up the WID and I could access the Other DB without the Password! If I do create a WIF for a database, how can I stop using it as if I never created it in the first place?
Is there anyone out there that can help me with this problem. I want to create a hyperlink in MS Outlook to my database file using my workgroup. The problem I'm having is when I put the following: file://"N:DbaseFilesSCC_Dbase.mdb" that works. It will open Access to that dbase file. But if I include the workgroup file associated like this: file://"N:DbaseFilesSCC_Dbase.mdb" /WRKGRP "N:DbaseFilesCSS_Issues.mdw" it doesn't work. Can someone please tell me why. I've been struggling with this for days now. I can't find any solutions.
My problem concerns importing a date from a txt file. I've been doing this for years with '97 and 2003 with no problem, but with 2007 I am now getting import errors which I can't resolve. The files, either fixed width or delimited, contain date information in the format ddmmyyyy (without any date separators). After importing I receive an import error message, and the relevant field in the table is blank.
In Access '97 or 2003 I can import date information directly into an Access date/time field by using an import specification where I have set the date delimiter to blank (by default this is set to "/" , so I simply delete this to leave the box empty). Using this method a file containing "25122007" (without the inverted commas) will be imported into Access as a date, and can be subsequently manipulated as date without having to resort to any fancy reformatting tricks. Obviously the import will not be sucessful if the date delimiter in the import spec is left as "/", or set to anything else, eg "." or ":".
But now that I've updated to Access 2007 this is just not possible no matter what I do or try. I can only import a date if the txt data has a separator, and that the same separator is set in the import specification.
In some new databases I have done a couple of workarounds, importing it as text into a text field, then using a CDate(Format(CLng([date]),"00/00/0000")) type expression in a subsequent query, but this is a pain having to do it, a really backward step.
But the real pain is older databases ('97 or 2003) which have been converted up to '07; they no longer work, and there is a lot of redesign to be done unless somone can tell me what I'm doing wrong.
Unfortunately I am not able to change the format of the dates in the data I receive, so the solution has to come from my end (ie Access). Surely Access 2007 should be able to recognise 25122007 as a date? All ideas gratefully received.
I've been happily using various versions of Access since 1994 and I've learnt lots along the way, and have always previously been able to sort out problems that I've come across without resorting to a forum, but I'm now really puzzled by a problem that I have come across in Access 2007. So although this is my first post I certainly wouldn't call myself a newbie. Hopefully I have described the problem accurately (it is realy simple in fact), but very happy to provide more information if required.
Hello people of access world forums. I've decided to design a simple access db with 2003 version but with 2000 compatibility and everything appear to work ok.
After designing and testing the db, I have set the Jet user-level security options as described in some documentation and set the startup options too for a "clean type" start. Everything is ok: I have created the workgroup in a new .mdw file, joined the workgroup, set the users, set the groups, protect the forms I wanted to. If I try to open the db, it asks for user and password and the db works as espected about security.
But if I delete, move or change the .mdw filename, the db turns accesible without the implemented security. Only the startup option works but no user is prompted and the protected items turns unprotected.
I would like to know how can I associate the .mdw to the .mdb so I can't access the .mdb if the .mdw file is not present (i.e. copying the .mdb to another computer or something).
I have a access 2003 database, and i am wondering if i can't setup a search function in a form that will open a file in windows explorer?
What i would like to do is have a test box that i enter in a number for example: 1234 then have a button named "Search" hit that button and it opens a corresponding file in windows explorer named 1234, or just opens that folder directly..
