>hi,
>
>I have my database i want to share to some of my colleagues for updating.
>i dont want to convert it to MDE because it is not finalize yet but is
>usable now.
>i want to share my database  to some of this users and i want to create
>users account.
>
>what would be my first step to this? can anyone guide me or give me some
>advice or link for any notes that i can read from.
>
>thanks..

"Tom van Stiphout" wrote:

> On Thu, 23 Oct 2008 23:22:04 -0700, Denver
> <Den***@discussions.microsoft.com> wrote:
>
> Your first statement doesn't make any sense. You *should* be deploying
> ..mde files for production, and keep the mdb file for yourself for
> further development.
>
> You should also split the db in front-end and back-end. Use a tool
> like Tony Toews auto-updater
> (http://www.granite.ab.ca/access/autofe.htm) to keep all users on the
> latest version of the FE.
>
> What are you trying to accomplish with user accounts? Note that
> user-level security is an advanced topic and you should not use it
> until you download, study, and fully understand the Microsoft Security
> FAQ.
> But there are other, simpler solutions. Just tell us what you want to
> do. How are you going to use the knowledge about who logged in? How
> secure do you need it to be?
>
> -Tom.
> Microsoft Access MVP
>
>
> >hi,
> >
> >I have my database i want to share to some of my colleagues for updating.
> >i dont want to convert it to MDE because it is not finalize yet but is
> >usable now.
> >i want to share my database  to some of this users and i want to create
> >users account.
> >
> >what would be my first step to this? can anyone guide me or give me some
> >advice or link for any notes that i can read from.
> >
> >thanks..
>

>Hello Tom van Stiphout,
>thanks for your reply...
>
>First thing is that i am not a programmer, new to access and don't have
>knowledge about security for database.
>
>2nd thing as you qouted,
>
>"But there are other, simpler solutions. Just tell us what you want to
>> do. How are you going to use the knowledge about who logged in? How
>> secure do you need it to be?
>
>**yes i just want the simpler solution. I want to set user account and
>permission like Read Only and similar. what would be my first step in
>accomplishing it? this is the thing i want to accomplish for now.  iam hoping
>Tom that you will be patience to guide until i have my last step in
>accomplishing it.
>
>thanks
>
>********************************************************
>"Tom van Stiphout" wrote:
>
>> On Thu, 23 Oct 2008 23:22:04 -0700, Denver
>> <Den***@discussions.microsoft.com> wrote:
>>
>> Your first statement doesn't make any sense. You *should* be deploying
>> ..mde files for production, and keep the mdb file for yourself for
>> further development.
>>
>> You should also split the db in front-end and back-end. Use a tool
>> like Tony Toews auto-updater
>> (http://www.granite.ab.ca/access/autofe.htm) to keep all users on the
>> latest version of the FE.
>>
>> What are you trying to accomplish with user accounts? Note that
>> user-level security is an advanced topic and you should not use it
>> until you download, study, and fully understand the Microsoft Security
>> FAQ.
>> But there are other, simpler solutions. Just tell us what you want to
>> do. How are you going to use the knowledge about who logged in? How
>> secure do you need it to be?
>>
>> -Tom.
>> Microsoft Access MVP
>>
>>
>> >hi,
>> >
>> >I have my database i want to share to some of my colleagues for updating.
>> >i dont want to convert it to MDE because it is not finalize yet but is
>> >usable now.
>> >i want to share my database  to some of this users and i want to create
>> >users account.
>> >
>> >what would be my first step to this? can anyone guide me or give me some
>> >advice or link for any notes that i can read from.
>> >
>> >thanks..
>>

"Tom van Stiphout" wrote:

> On Sat, 25 Oct 2008 00:24:01 -0700, Denver
> <Den***@discussions.microsoft.com> wrote:
>
> I can't guarantee that. However you're free to post back to the
> newsgroup at any time.
> I'm going to present a simple solution. Not the most secure or the
> most features. Simple.
>
> First thing we need is to find out who is using the app. Just ask
> Windows who is logged in. See
> http://www.mvps.org/access/api/api0008.htm for the code. Put this in a
> standard module.
>
> Next you need a table (say tblSecurity) with UserName (make this the
> Primary key) and a bunch of Yes/No permission fields. If this were the
> Northwind sample application I might have fields like IsAdministrator,
> CanEnterOrders, CanViewOrders, etc.
>
> Last is to write some one-liners in various places to check the
> permissions. For example in the Orders form's Form_Open I would write:
> if dlookup("CanViewOrders", "tblSecurity", "UserName='" &
> fOSUserName() & "'") = False then Cancel = True
> (note how the username is wrapped in single-quotes)
> With this line I am checking if the CanViewOrders YesNo field in the
> security table is set to False, and if it is, I set Cancel=True which
> conveniently stops the opening of that form.
> Why don't I write this code in the menu option or button click that
> opens the form? Because there may be several ways to open the form and
> I would have to be very careful not to forget any. The way I did it I
> would have to write code only in one location.
>
> To give someone readonly access I would set the form's AllowEdits
> property to False:
> (also in the Form_Open)
> if dlookup("CanEditOrders", "tblSecurity", "UserName="" &
> fOSUserName() & "'") = False then Me.AllowEdits=True
>
> -Tom.
>
>
>
> >Hello Tom van Stiphout,
> >thanks for your reply...
> >
> >First thing is that i am not a programmer, new to access and don't have
> >knowledge about security for database.
> >
> >2nd thing as you qouted,
> >
> >"But there are other, simpler solutions. Just tell us what you want to
> >> do. How are you going to use the knowledge about who logged in? How
> >> secure do you need it to be?
> >
> >**yes i just want the simpler solution. I want to set user account and
> >permission like Read Only and similar. what would be my first step in
> >accomplishing it? this is the thing i want to accomplish for now.  iam hoping
> >Tom that you will be patience to guide until i have my last step in
> >accomplishing it.
> >
> >thanks
> >
> >********************************************************
> >"Tom van Stiphout" wrote:
> >
> >> On Thu, 23 Oct 2008 23:22:04 -0700, Denver
> >> <Den***@discussions.microsoft.com> wrote:
> >>
> >> Your first statement doesn't make any sense. You *should* be deploying
> >> ..mde files for production, and keep the mdb file for yourself for
> >> further development.
> >>
> >> You should also split the db in front-end and back-end. Use a tool
> >> like Tony Toews auto-updater
> >> (http://www.granite.ab.ca/access/autofe.htm) to keep all users on the
> >> latest version of the FE.
> >>
> >> What are you trying to accomplish with user accounts? Note that
> >> user-level security is an advanced topic and you should not use it
> >> until you download, study, and fully understand the Microsoft Security
> >> FAQ.
> >> But there are other, simpler solutions. Just tell us what you want to
> >> do. How are you going to use the knowledge about who logged in? How
> >> secure do you need it to be?
> >>
> >> -Tom.
> >> Microsoft Access MVP
> >>
> >>
> >> >hi,
> >> >
> >> >I have my database i want to share to some of my colleagues for updating.
> >> >i dont want to convert it to MDE because it is not finalize yet but is
> >> >usable now.
> >> >i want to share my database  to some of this users and i want to create
> >> >users account.
> >> >
> >> >what would be my first step to this? can anyone guide me or give me some
> >> >advice or link for any notes that i can read from.
> >> >
> >> >thanks..
> >>
>

>Hello Tom,
>
>I think i alreday done with the first ang 2nd step
>now i have my table name User & Permission...
>i have Yes/no Fields
>i have the following........
>R_W - read and write permission but cannot delete or modfiy existing reocrds
>or data
>R_W_D - read, write, modify can alse delete or modify any existing records
>or data
>Read Only - for read only permission
>Administrator - full permission
>is this correct?does this make sense or do i need to add more Yes/No fields,
>what would those be?
>
>i have already done with the modules and named it fOSUsername.
>i also have the form that is bound for user and permission table
>i also have the log in forms where user log thru typing there user name and
>password....
>
>what would be the next thing to do? where do i put this dlookup functions as
>the sample you give me? i only have 4 user to include myself for my database
>for now. i dont want to convert this to MDE due to time constraint. what is
>important for me is to fill the necessary DATA.
>
>thanks Tom van Stiphout...
>
>**********************************************************
>
>"Tom van Stiphout" wrote:
>
>> On Sat, 25 Oct 2008 00:24:01 -0700, Denver
>> <Den***@discussions.microsoft.com> wrote:
>>
>> I can't guarantee that. However you're free to post back to the
>> newsgroup at any time.
>> I'm going to present a simple solution. Not the most secure or the
>> most features. Simple.
>>
>> First thing we need is to find out who is using the app. Just ask
>> Windows who is logged in. See
>> http://www.mvps.org/access/api/api0008.htm for the code. Put this in a
>> standard module.
>>
>> Next you need a table (say tblSecurity) with UserName (make this the
>> Primary key) and a bunch of Yes/No permission fields. If this were the
>> Northwind sample application I might have fields like IsAdministrator,
>> CanEnterOrders, CanViewOrders, etc.
>>
>> Last is to write some one-liners in various places to check the
>> permissions. For example in the Orders form's Form_Open I would write:
>> if dlookup("CanViewOrders", "tblSecurity", "UserName='" &
>> fOSUserName() & "'") = False then Cancel = True
>> (note how the username is wrapped in single-quotes)
>> With this line I am checking if the CanViewOrders YesNo field in the
>> security table is set to False, and if it is, I set Cancel=True which
>> conveniently stops the opening of that form.
>> Why don't I write this code in the menu option or button click that
>> opens the form? Because there may be several ways to open the form and
>> I would have to be very careful not to forget any. The way I did it I
>> would have to write code only in one location.
>>
>> To give someone readonly access I would set the form's AllowEdits
>> property to False:
>> (also in the Form_Open)
>> if dlookup("CanEditOrders", "tblSecurity", "UserName="" &
>> fOSUserName() & "'") = False then Me.AllowEdits=True
>>
>> -Tom.
>>
>>
>>
>> >Hello Tom van Stiphout,
>> >thanks for your reply...
>> >
>> >First thing is that i am not a programmer, new to access and don't have
>> >knowledge about security for database.
>> >
>> >2nd thing as you qouted,
>> >
>> >"But there are other, simpler solutions. Just tell us what you want to
>> >> do. How are you going to use the knowledge about who logged in? How
>> >> secure do you need it to be?
>> >
>> >**yes i just want the simpler solution. I want to set user account and
>> >permission like Read Only and similar. what would be my first step in
>> >accomplishing it? this is the thing i want to accomplish for now.  iam hoping
>> >Tom that you will be patience to guide until i have my last step in
>> >accomplishing it.
>> >
>> >thanks
>> >
>> >********************************************************
>> >"Tom van Stiphout" wrote:
>> >
>> >> On Thu, 23 Oct 2008 23:22:04 -0700, Denver
>> >> <Den***@discussions.microsoft.com> wrote:
>> >>
>> >> Your first statement doesn't make any sense. You *should* be deploying
>> >> ..mde files for production, and keep the mdb file for yourself for
>> >> further development.
>> >>
>> >> You should also split the db in front-end and back-end. Use a tool
>> >> like Tony Toews auto-updater
>> >> (http://www.granite.ab.ca/access/autofe.htm) to keep all users on the
>> >> latest version of the FE.
>> >>
>> >> What are you trying to accomplish with user accounts? Note that
>> >> user-level security is an advanced topic and you should not use it
>> >> until you download, study, and fully understand the Microsoft Security
>> >> FAQ.
>> >> But there are other, simpler solutions. Just tell us what you want to
>> >> do. How are you going to use the knowledge about who logged in? How
>> >> secure do you need it to be?
>> >>
>> >> -Tom.
>> >> Microsoft Access MVP
>> >>
>> >>
>> >> >hi,
>> >> >
>> >> >I have my database i want to share to some of my colleagues for updating.
>> >> >i dont want to convert it to MDE because it is not finalize yet but is
>> >> >usable now.
>> >> >i want to share my database  to some of this users and i want to create
>> >> >users account.
>> >> >
>> >> >what would be my first step to this? can anyone guide me or give me some
>> >> >advice or link for any notes that i can read from.
>> >> >
>> >> >thanks..
>> >>
>>

"Tom van Stiphout" wrote:

> On Sun, 26 Oct 2008 21:11:00 -0700, Denver
> <Den***@discussions.microsoft.com> wrote:
>
> As I have shown: you write your code in each Form_Open event. In
> addition to AllowEdits we have AllowAdditions and AllowDeletes.
>
> Creating an MDE takes only 1 minute.
>
> -Tom.
> Microsoft Access MVP
>
>
> >Hello Tom,
> >
> >I think i alreday done with the first ang 2nd step
> >now i have my table name User & Permission...
> >i have Yes/no Fields
> >i have the following........
> >R_W - read and write permission but cannot delete or modfiy existing reocrds
> >or data
> >R_W_D - read, write, modify can alse delete or modify any existing records
> >or data
> >Read Only - for read only permission
> >Administrator - full permission
> >is this correct?does this make sense or do i need to add more Yes/No fields,
> >what would those be?
> >
> >i have already done with the modules and named it fOSUsername.
> >i also have the form that is bound for user and permission table
> >i also have the log in forms where user log thru typing there user name and
> >password....
> >
> >what would be the next thing to do? where do i put this dlookup functions as
> >the sample you give me? i only have 4 user to include myself for my database
> >for now. i dont want to convert this to MDE due to time constraint. what is
> >important for me is to fill the necessary DATA.
> >
> >thanks Tom van Stiphout...
> >
> >**********************************************************
> >
> >"Tom van Stiphout" wrote:
> >
> >> On Sat, 25 Oct 2008 00:24:01 -0700, Denver
> >> <Den***@discussions.microsoft.com> wrote:
> >>
> >> I can't guarantee that. However you're free to post back to the
> >> newsgroup at any time.
> >> I'm going to present a simple solution. Not the most secure or the
> >> most features. Simple.
> >>
> >> First thing we need is to find out who is using the app. Just ask
> >> Windows who is logged in. See
> >> http://www.mvps.org/access/api/api0008.htm for the code. Put this in a
> >> standard module.
> >>
> >> Next you need a table (say tblSecurity) with UserName (make this the
> >> Primary key) and a bunch of Yes/No permission fields. If this were the
> >> Northwind sample application I might have fields like IsAdministrator,
> >> CanEnterOrders, CanViewOrders, etc.
> >>
> >> Last is to write some one-liners in various places to check the
> >> permissions. For example in the Orders form's Form_Open I would write:
> >> if dlookup("CanViewOrders", "tblSecurity", "UserName='" &
> >> fOSUserName() & "'") = False then Cancel = True
> >> (note how the username is wrapped in single-quotes)
> >> With this line I am checking if the CanViewOrders YesNo field in the
> >> security table is set to False, and if it is, I set Cancel=True which
> >> conveniently stops the opening of that form.
> >> Why don't I write this code in the menu option or button click that
> >> opens the form? Because there may be several ways to open the form and
> >> I would have to be very careful not to forget any. The way I did it I
> >> would have to write code only in one location.
> >>
> >> To give someone readonly access I would set the form's AllowEdits
> >> property to False:
> >> (also in the Form_Open)
> >> if dlookup("CanEditOrders", "tblSecurity", "UserName="" &
> >> fOSUserName() & "'") = False then Me.AllowEdits=True
> >>
> >> -Tom.
> >>
> >>
> >>
> >> >Hello Tom van Stiphout,
> >> >thanks for your reply...
> >> >
> >> >First thing is that i am not a programmer, new to access and don't have
> >> >knowledge about security for database.
> >> >
> >> >2nd thing as you qouted,
> >> >
> >> >"But there are other, simpler solutions. Just tell us what you want to
> >> >> do. How are you going to use the knowledge about who logged in? How
> >> >> secure do you need it to be?
> >> >
> >> >**yes i just want the simpler solution. I want to set user account and
> >> >permission like Read Only and similar. what would be my first step in
> >> >accomplishing it? this is the thing i want to accomplish for now.  iam hoping
> >> >Tom that you will be patience to guide until i have my last step in
> >> >accomplishing it.
> >> >
> >> >thanks
> >> >
> >> >********************************************************
> >> >"Tom van Stiphout" wrote:
> >> >
> >> >> On Thu, 23 Oct 2008 23:22:04 -0700, Denver
> >> >> <Den***@discussions.microsoft.com> wrote:
> >> >>
> >> >> Your first statement doesn't make any sense. You *should* be deploying
> >> >> ..mde files for production, and keep the mdb file for yourself for
> >> >> further development.
> >> >>
> >> >> You should also split the db in front-end and back-end. Use a tool
> >> >> like Tony Toews auto-updater
> >> >> (http://www.granite.ab.ca/access/autofe.htm) to keep all users on the
> >> >> latest version of the FE.
> >> >>
> >> >> What are you trying to accomplish with user accounts? Note that
> >> >> user-level security is an advanced topic and you should not use it
> >> >> until you download, study, and fully understand the Microsoft Security
> >> >> FAQ.
> >> >> But there are other, simpler solutions. Just tell us what you want to
> >> >> do. How are you going to use the knowledge about who logged in? How
> >> >> secure do you need it to be?
> >> >>
> >> >> -Tom.
> >> >> Microsoft Access MVP
> >> >>
> >> >>
> >> >> >hi,
> >> >> >
> >> >> >I have my database i want to share to some of my colleagues for updating.
> >> >> >i dont want to convert it to MDE because it is not finalize yet but is
> >> >> >usable now.
> >> >> >i want to share my database  to some of this users and i want to create
> >> >> >users account.
> >> >> >
> >> >> >what would be my first step to this? can anyone guide me or give me some
> >> >> >advice or link for any notes that i can read from.
> >> >> >
> >> >> >thanks..
> >> >>
> >>
>

>Hello Tom,
>
>when i try to convert my database to MDE i have this Error....
>
>Microsoft Office Access was unable to create an MDE database.
> and i open the Window Help and i prompts as follow..
>
>is there any prior procedure in converting MDE thats why i have this error?
>or maybe i need to complie my VBA codes? is there anyway i can get rid of
>this error?
>......
>This error is usually associated with compiling a large database into an MDE
>file.  Due to the method used to compile the database, a considerable number
>of TableID references are created for each table.  The Microsoft Jet database
>engine version 4.0 can only create a maximum of 2048 open TableIDs at one
>time.  Exporting a database as an MDE potentially can exceed this limit if
>the database has a large number of objects (table, macro, form, report, etc).
>There is no accurate method to estimate the number of TableIDs the Jet
>database engine uses during the process of compiling a database as an MDE. 
>However, each VBA module and each form uses one TableID, as a result, if the
>database has 500 forms, and each form's HasModule property is set to Yes, as
>many as 1,000 TableIDs are used.
>
>
>
>Thanks
>
>*********************************************************
>
>"Tom van Stiphout" wrote:
>
>> On Sun, 26 Oct 2008 21:11:00 -0700, Denver
>> <Den***@discussions.microsoft.com> wrote:
>>
>> As I have shown: you write your code in each Form_Open event. In
>> addition to AllowEdits we have AllowAdditions and AllowDeletes.
>>
>> Creating an MDE takes only 1 minute.
>>
>> -Tom.
>> Microsoft Access MVP
>>
>>
>> >Hello Tom,
>> >
>> >I think i alreday done with the first ang 2nd step
>> >now i have my table name User & Permission...
>> >i have Yes/no Fields
>> >i have the following........
>> >R_W - read and write permission but cannot delete or modfiy existing reocrds
>> >or data
>> >R_W_D - read, write, modify can alse delete or modify any existing records
>> >or data
>> >Read Only - for read only permission
>> >Administrator - full permission
>> >is this correct?does this make sense or do i need to add more Yes/No fields,
>> >what would those be?
>> >
>> >i have already done with the modules and named it fOSUsername.
>> >i also have the form that is bound for user and permission table
>> >i also have the log in forms where user log thru typing there user name and
>> >password....
>> >
>> >what would be the next thing to do? where do i put this dlookup functions as
>> >the sample you give me? i only have 4 user to include myself for my database
>> >for now. i dont want to convert this to MDE due to time constraint. what is
>> >important for me is to fill the necessary DATA.
>> >
>> >thanks Tom van Stiphout...
>> >
>> >**********************************************************
>> >
>> >"Tom van Stiphout" wrote:
>> >
>> >> On Sat, 25 Oct 2008 00:24:01 -0700, Denver
>> >> <Den***@discussions.microsoft.com> wrote:
>> >>
>> >> I can't guarantee that. However you're free to post back to the
>> >> newsgroup at any time.
>> >> I'm going to present a simple solution. Not the most secure or the
>> >> most features. Simple.
>> >>
>> >> First thing we need is to find out who is using the app. Just ask
>> >> Windows who is logged in. See
>> >> http://www.mvps.org/access/api/api0008.htm for the code. Put this in a
>> >> standard module.
>> >>
>> >> Next you need a table (say tblSecurity) with UserName (make this the
>> >> Primary key) and a bunch of Yes/No permission fields. If this were the
>> >> Northwind sample application I might have fields like IsAdministrator,
>> >> CanEnterOrders, CanViewOrders, etc.
>> >>
>> >> Last is to write some one-liners in various places to check the
>> >> permissions. For example in the Orders form's Form_Open I would write:
>> >> if dlookup("CanViewOrders", "tblSecurity", "UserName='" &
>> >> fOSUserName() & "'") = False then Cancel = True
>> >> (note how the username is wrapped in single-quotes)
>> >> With this line I am checking if the CanViewOrders YesNo field in the
>> >> security table is set to False, and if it is, I set Cancel=True which
>> >> conveniently stops the opening of that form.
>> >> Why don't I write this code in the menu option or button click that
>> >> opens the form? Because there may be several ways to open the form and
>> >> I would have to be very careful not to forget any. The way I did it I
>> >> would have to write code only in one location.
>> >>
>> >> To give someone readonly access I would set the form's AllowEdits
>> >> property to False:
>> >> (also in the Form_Open)
>> >> if dlookup("CanEditOrders", "tblSecurity", "UserName="" &
>> >> fOSUserName() & "'") = False then Me.AllowEdits=True
>> >>
>> >> -Tom.
>> >>
>> >>
>> >>
>> >> >Hello Tom van Stiphout,
>> >> >thanks for your reply...
>> >> >
>> >> >First thing is that i am not a programmer, new to access and don't have
>> >> >knowledge about security for database.
>> >> >
>> >> >2nd thing as you qouted,
>> >> >
>> >> >"But there are other, simpler solutions. Just tell us what you want to
>> >> >> do. How are you going to use the knowledge about who logged in? How
>> >> >> secure do you need it to be?
>> >> >
>> >> >**yes i just want the simpler solution. I want to set user account and
>> >> >permission like Read Only and similar. what would be my first step in
>> >> >accomplishing it? this is the thing i want to accomplish for now.  iam hoping
>> >> >Tom that you will be patience to guide until i have my last step in
>> >> >accomplishing it.
>> >> >
>> >> >thanks
>> >> >
>> >> >********************************************************
>> >> >"Tom van Stiphout" wrote:
>> >> >
>> >> >> On Thu, 23 Oct 2008 23:22:04 -0700, Denver
>> >> >> <Den***@discussions.microsoft.com> wrote:
>> >> >>
>> >> >> Your first statement doesn't make any sense. You *should* be deploying
>> >> >> ..mde files for production, and keep the mdb file for yourself for
>> >> >> further development.
>> >> >>
>> >> >> You should also split the db in front-end and back-end. Use a tool
>> >> >> like Tony Toews auto-updater
>> >> >> (http://www.granite.ab.ca/access/autofe.htm) to keep all users on the
>> >> >> latest version of the FE.
>> >> >>
>> >> >> What are you trying to accomplish with user accounts? Note that
>> >> >> user-level security is an advanced topic and you should not use it
>> >> >> until you download, study, and fully understand the Microsoft Security
>> >> >> FAQ.
>> >> >> But there are other, simpler solutions. Just tell us what you want to
>> >> >> do. How are you going to use the knowledge about who logged in? How
>> >> >> secure do you need it to be?
>> >> >>
>> >> >> -Tom.
>> >> >> Microsoft Access MVP
>> >> >>
>> >> >>
>> >> >> >hi,
>> >> >> >
>> >> >> >I have my database i want to share to some of my colleagues for updating.
>> >> >> >i dont want to convert it to MDE because it is not finalize yet but is
>> >> >> >usable now.
>> >> >> >i want to share my database  to some of this users and i want to create
>> >> >> >users account.
>> >> >> >
>> >> >> >what would be my first step to this? can anyone guide me or give me some
>> >> >> >advice or link for any notes that i can read from.
>> >> >> >
>> >> >> >thanks..
>> >> >>
>> >>
>>

"Tom van Stiphout" wrote:

> On Tue, 28 Oct 2008 08:32:25 -0700, Denver
> <Den***@discussions.microsoft.com> wrote:
>
> Open a code window and select menu option Debug > Compile. Fix any
> problems it points out.
>
> -Tom.
> Microsoft Access MVP
>
>
> >Hello Tom,
> >
> >when i try to convert my database to MDE i have this Error....
> >
> >Microsoft Office Access was unable to create an MDE database.
> > and i open the Window Help and i prompts as follow..
> >
> >is there any prior procedure in converting MDE thats why i have this error?
> >or maybe i need to complie my VBA codes? is there anyway i can get rid of
> >this error?
> >......
> >This error is usually associated with compiling a large database into an MDE
> >file.  Due to the method used to compile the database, a considerable number
> >of TableID references are created for each table.  The Microsoft Jet database
> >engine version 4.0 can only create a maximum of 2048 open TableIDs at one
> >time.  Exporting a database as an MDE potentially can exceed this limit if
> >the database has a large number of objects (table, macro, form, report, etc).
> >There is no accurate method to estimate the number of TableIDs the Jet
> >database engine uses during the process of compiling a database as an MDE. 
> >However, each VBA module and each form uses one TableID, as a result, if the
> >database has 500 forms, and each form's HasModule property is set to Yes, as
> >many as 1,000 TableIDs are used.
> >
> >
> >
> >Thanks
> >
> >*********************************************************
> >
> >"Tom van Stiphout" wrote:
> >
> >> On Sun, 26 Oct 2008 21:11:00 -0700, Denver
> >> <Den***@discussions.microsoft.com> wrote:
> >>
> >> As I have shown: you write your code in each Form_Open event. In
> >> addition to AllowEdits we have AllowAdditions and AllowDeletes.
> >>
> >> Creating an MDE takes only 1 minute.
> >>
> >> -Tom.
> >> Microsoft Access MVP
> >>
> >>
> >> >Hello Tom,
> >> >
> >> >I think i alreday done with the first ang 2nd step
> >> >now i have my table name User & Permission...
> >> >i have Yes/no Fields
> >> >i have the following........
> >> >R_W - read and write permission but cannot delete or modfiy existing reocrds
> >> >or data
> >> >R_W_D - read, write, modify can alse delete or modify any existing records
> >> >or data
> >> >Read Only - for read only permission
> >> >Administrator - full permission
> >> >is this correct?does this make sense or do i need to add more Yes/No fields,
> >> >what would those be?
> >> >
> >> >i have already done with the modules and named it fOSUsername.
> >> >i also have the form that is bound for user and permission table
> >> >i also have the log in forms where user log thru typing there user name and
> >> >password....
> >> >
> >> >what would be the next thing to do? where do i put this dlookup functions as
> >> >the sample you give me? i only have 4 user to include myself for my database
> >> >for now. i dont want to convert this to MDE due to time constraint. what is
> >> >important for me is to fill the necessary DATA.
> >> >
> >> >thanks Tom van Stiphout...
> >> >
> >> >**********************************************************
> >> >
> >> >"Tom van Stiphout" wrote:
> >> >
> >> >> On Sat, 25 Oct 2008 00:24:01 -0700, Denver
> >> >> <Den***@discussions.microsoft.com> wrote:
> >> >>
> >> >> I can't guarantee that. However you're free to post back to the
> >> >> newsgroup at any time.
> >> >> I'm going to present a simple solution. Not the most secure or the
> >> >> most features. Simple.
> >> >>
> >> >> First thing we need is to find out who is using the app. Just ask
> >> >> Windows who is logged in. See
> >> >> http://www.mvps.org/access/api/api0008.htm for the code. Put this in a
> >> >> standard module.
> >> >>
> >> >> Next you need a table (say tblSecurity) with UserName (make this the
> >> >> Primary key) and a bunch of Yes/No permission fields. If this were the
> >> >> Northwind sample application I might have fields like IsAdministrator,
> >> >> CanEnterOrders, CanViewOrders, etc.
> >> >>
> >> >> Last is to write some one-liners in various places to check the
> >> >> permissions. For example in the Orders form's Form_Open I would write:
> >> >> if dlookup("CanViewOrders", "tblSecurity", "UserName='" &
> >> >> fOSUserName() & "'") = False then Cancel = True
> >> >> (note how the username is wrapped in single-quotes)
> >> >> With this line I am checking if the CanViewOrders YesNo field in the
> >> >> security table is set to False, and if it is, I set Cancel=True which
> >> >> conveniently stops the opening of that form.
> >> >> Why don't I write this code in the menu option or button click that
> >> >> opens the form? Because there may be several ways to open the form and
> >> >> I would have to be very careful not to forget any. The way I did it I
> >> >> would have to write code only in one location.
> >> >>
> >> >> To give someone readonly access I would set the form's AllowEdits
> >> >> property to False:
> >> >> (also in the Form_Open)
> >> >> if dlookup("CanEditOrders", "tblSecurity", "UserName="" &
> >> >> fOSUserName() & "'") = False then Me.AllowEdits=True
> >> >>
> >> >> -Tom.
> >> >>
> >> >>
> >> >>
> >> >> >Hello Tom van Stiphout,
> >> >> >thanks for your reply...
> >> >> >
> >> >> >First thing is that i am not a programmer, new to access and don't have
> >> >> >knowledge about security for database.
> >> >> >
> >> >> >2nd thing as you qouted,
> >> >> >
> >> >> >"But there are other, simpler solutions. Just tell us what you want to
> >> >> >> do. How are you going to use the knowledge about who logged in? How
> >> >> >> secure do you need it to be?
> >> >> >
> >> >> >**yes i just want the simpler solution. I want to set user account and
> >> >> >permission like Read Only and similar. what would be my first step in
> >> >> >accomplishing it? this is the thing i want to accomplish for now.  iam hoping
> >> >> >Tom that you will be patience to guide until i have my last step in
> >> >> >accomplishing it.
> >> >> >
> >> >> >thanks
> >> >> >
> >> >> >********************************************************
> >> >> >"Tom van Stiphout" wrote:
> >> >> >
> >> >> >> On Thu, 23 Oct 2008 23:22:04 -0700, Denver
> >> >> >> <Den***@discussions.microsoft.com> wrote:
> >> >> >>
> >> >> >> Your first statement doesn't make any sense. You *should* be deploying
> >> >> >> ..mde files for production, and keep the mdb file for yourself for
> >> >> >> further development.
> >> >> >>
> >> >> >> You should also split the db in front-end and back-end. Use a tool
> >> >> >> like Tony Toews auto-updater
> >> >> >> (http://www.granite.ab.ca/access/autofe.htm) to keep all users on the
> >> >> >> latest version of the FE.
> >> >> >>
> >> >> >> What are you trying to accomplish with user accounts? Note that
> >> >> >> user-level security is an advanced topic and you should not use it
> >> >> >> until you download, study, and fully understand the Microsoft Security
> >> >> >> FAQ.
> >> >> >> But there are other, simpler solutions. Just tell us what you want to
> >> >> >> do. How are you going to use the knowledge about who logged in? How
> >> >> >> secure do you need it to be?
> >> >> >>
> >> >> >> -Tom.
> >> >> >> Microsoft Access MVP
> >> >> >>
> >> >> >>
> >> >> >> >hi,
> >> >> >> >
> >> >> >> >I have my database i want to share to some of my colleagues for updating.
> >> >> >> >i dont want to convert it to MDE because it is not finalize yet but is
> >> >> >> >usable now.
> >> >> >> >i want to share my database  to some of this users and i want to create
> >> >> >> >users account.
> >> >> >> >
> >> >> >> >what would be my first step to this? can anyone guide me or give me some
> >> >> >> >advice or link for any notes that i can read from.
> >> >> >> >
> >> >> >> >thanks..
> >> >> >>
> >> >>
> >>
>