Access 2003

[mseo]

Hi
I have an access 2003 DataBase I have designed it on my computer and when I copied it to another computer I got built-in login form asking me for user name and password
and I have never created any kind of security to this database so I had to open it exclusively so I need what's the reason of that and how can i handle this problem
again I have the full-open database on my computer
thanks for any help you my provide me.

[mseo]

the operating system of my computer is a Vista and the computer that I have tried to use it on is XP please I have tried to solve this, but I can't , I feel like I have to restructure the database again

[Delerna]

Nothing comes to mind as to why it is doing that except some sort of compatibility issue. I seem to recall a similar thing happening to me when the company I was working for at the time had a mix of computers running Windows 98 and XP. Don't remember the details but I think I finished up keeping 2 versions of the database.

Try creating a new database on the XP machine and then importing all the objects into it from the orriginal DB. See if that gets you around the problem.
Hopefully someone else might have a better answer.
It sounds like the sort of problem that requires physical access to everything involved in order to solve.

[NeoPa]

Access security is set up as a PC level entity. If the standard System.Mda is used on your PC it's possible that a modified version is on the other. It is Access that this pertains to rather than a specific database though. You should notice this happens on the other PC for all usage, not just your database.

[Delerna]

Just reread my post and wanted to clarify that the

similar

thing I mentioned had nothing to do with security.
It was more, it ran fine on XP but not on 98

[mseo]

thanks for your replies and I have found that when I moved the access file to another PC the default administration group has been changed
and my question now why have I had to assign the group to open the database?
and in fact I didn't create any groups or any kind of security
thank you very much and I appreciate your replies.

[Stewart Ross]

The problem with Access workgroup files, as NeoPa said, is that if such a workgroup is created for a particular installation it is then applied by default to all MS Access databases opened using that installation. It is for this reason that you have such a workgroup being applied when you didn't define one for your database.

You may be able to change the default workgroup for the installation that is causing you difficulties (if you have suitable permissions). If the workgroup was defined for a specific application it can still be used for that application by opening it from a command line - the /wrkgrp switch can be set to specify which workgroup to use.

-Stewart

[NeoPa]

Unless you're very comfortable with these security files (typically SYSTEM.MDW - Apologies for referring to it as MDA in the earlier post), and very few are - hence their removal in later releases, I suggest you leave the basic security as it is.

I would echo Stewart's comment. When, and only when, necessary, apply a specific security file to a project using the command line switch. That way others, like yourself, won't have these confusing situations to fall over.

It's a design flaw (from Access) in my view, which you have stumbled over. Whoever left you the situation by changing the file on one PC should not be blamed too heavily as it's a difficult area to navigate.