MS access form design mode

[Guest]

I am currently using an ms access database that doesn't have the normal menu.

I opened the application pressing the shift key. It has "File" and other
application specific menus. I did an F11. After a form is opened in design
mode, it doesn't show the "view" option in the menu toolbar. So, there's no
way to see the code, properties etc .. Also, the application specific menus
still remain.

Also, "Tools" menu has only two options in it. "Hyperlink" and "Compact
Repair Database". It doesn't have relationships etc..

This is the copy of a prod database and I am supposed to make some changes
to it per requirements. Is there a way to see the "view" menu and "code"? Do
I have to request a development version of it?

Is exporting the database only option. If so, can I export all tables/forms
at once instead of exporting each table or form? It takes long and is
painstaking to export every single object.

Thanks in advance.

 

[Albert D.Kallal]

Typically, if you ask most access developers the following question:

should one prevent the end user from seeing all of the ms-access stuff
they don't need?

Answer: = yes...

So, typically, a very large portion of developers do hide all of the access
interface.

If holding down the shift key does not get you the full menus and full
access to design mode, then either you are not using the shift key correctly
to get in, or the developer has set the shift key by-pass.

It is *very* easy to figure out of the shift key by-pass is working, since
if you launch the application normal, and a "main" form displays, then that
is normal. IF you hold down the shift key, and the main application startup
form *still* displays, then you did not use the shift key correctly, or the
application is setup to ignore the shift key.

There is not use tying to get other menus etc to display if you don't have
the shift key by-pass working.

Give my shift key setter a try here:
http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html

Te above simply allows you to browse to a mdb file..and disable the shift
key....

Try the above..

Is exporting the database only option

Why not create a blank mdb file..and simply import everything? The normal
way to "copy" all forms, or table, or reports or whatever is to simply use
file->get external data. The import options allows you to do this
"wholesale", and you don't have to do this one by one...

 

[Albert D.Kallal]

Typically, if you ask most access developers the following question:

should one prevent the end user from seeing all of the ms-access stuff
they don't need?

Answer: = yes...

So, typically, a very large portion of developers do hide all of the access
interface.

If holding down the shift key does not get you the full menus and full
access to design mode, then either you are not using the shift key correctly
to get in, or the developer has set the shift key by-pass.

It is *very* easy to figure out of the shift key by-pass is working, since
if you launch the application normal, and a "main" form displays, then that
is normal. IF you hold down the shift key, and the main application startup
form *still* displays, then you did not use the shift key correctly, or the
application is setup to ignore the shift key.

There is not use tying to get other menus etc to display if you don't have
the shift key by-pass working.

Give my shift key setter a try here:
http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html

Te above simply allows you to browse to a mdb file..and disable the shift
key....

Try the above..

Is exporting the database only option

Why not create a blank mdb file..and simply import everything? The normal
way to "copy" all forms, or table, or reports or whatever is to simply use
file->get external data. The import options allows you to do this
"wholesale", and you don't have to do this one by one...

 

[Pieter Wijnen]

Or it's a runtime...

Pieter

Typically, if you ask most access developers the following question:

should one prevent the end user from seeing all of the ms-access stuff
they don't need?

Answer: = yes...

So, typically, a very large portion of developers do hide all of the
access interface.

If holding down the shift key does not get you the full menus and full
access to design mode, then either you are not using the shift key
correctly to get in, or the developer has set the shift key by-pass.

It is *very* easy to figure out of the shift key by-pass is working, since
if you launch the application normal, and a "main" form displays, then
that is normal. IF you hold down the shift key, and the main application
startup form *still* displays, then you did not use the shift key
correctly, or the application is setup to ignore the shift key.

There is not use tying to get other menus etc to display if you don't have
the shift key by-pass working.

Give my shift key setter a try here:
http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html

Te above simply allows you to browse to a mdb file..and disable the shift
key....

Try the above..


Why not create a blank mdb file..and simply import everything? The normal
way to "copy" all forms, or table, or reports or whatever is to simply
use file->get external data. The import options allows you to do this
"wholesale", and you don't have to do this one by one...

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(e-mail address removed)
http://www.members.shaw.ca/AlbertKallal

 

[Pieter Wijnen]

Or it's a runtime...

Pieter

Typically, if you ask most access developers the following question:

should one prevent the end user from seeing all of the ms-access stuff
they don't need?

Answer: = yes...

So, typically, a very large portion of developers do hide all of the
access interface.

If holding down the shift key does not get you the full menus and full
access to design mode, then either you are not using the shift key
correctly to get in, or the developer has set the shift key by-pass.

It is *very* easy to figure out of the shift key by-pass is working, since
if you launch the application normal, and a "main" form displays, then
that is normal. IF you hold down the shift key, and the main application
startup form *still* displays, then you did not use the shift key
correctly, or the application is setup to ignore the shift key.

There is not use tying to get other menus etc to display if you don't have
the shift key by-pass working.

Give my shift key setter a try here:
http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html

Te above simply allows you to browse to a mdb file..and disable the shift
key....

Try the above..


Why not create a blank mdb file..and simply import everything? The normal
way to "copy" all forms, or table, or reports or whatever is to simply
use file->get external data. The import options allows you to do this
"wholesale", and you don't have to do this one by one...

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(e-mail address removed)
http://www.members.shaw.ca/AlbertKallal

 

[Guest]

Hi this is probably a dumb question. Its an mdb file. How do I distinguish if
its a runtime/development file. Are there any things noticeable/check for? I
just imported the objects into a new database.

I tried holding the shift key. Its the same. No difference.
However, I'd like to modify the application without shift key bypass. The
end users expect me to make changes. Should I ask them a dev version of
application? Is it my job to import and then use the new database? However,
eventually, I should give them the original application with the
modifications.

Is it an issue? Are they supposed to give me an application without shiftkey
bypass?

 

[Guest]

Hi this is probably a dumb question. Its an mdb file. How do I distinguish if
its a runtime/development file. Are there any things noticeable/check for? I
just imported the objects into a new database.

I tried holding the shift key. Its the same. No difference.
However, I'd like to modify the application without shift key bypass. The
end users expect me to make changes. Should I ask them a dev version of
application? Is it my job to import and then use the new database? However,
eventually, I should give them the original application with the
modifications.

Is it an issue? Are they supposed to give me an application without shiftkey
bypass?

 

[Pieter Wijnen]

runtime applies to the msaccess.exe - not the mdb
can you access the modules by pressing ctrl+g?
if not you have to ask them to remove the flags or alter the properities
stopping you from another mdb

I believe it's Application.SetOption("Use Access Special Keys")=True
or db.properties("AllowSpecialKeys") = True
for the shift key
db.properties("AllowBypassKey") = true

But i think there's an example at www.mvps.org/access

hth

Pieter

 

[Pieter Wijnen]

runtime applies to the msaccess.exe - not the mdb
can you access the modules by pressing ctrl+g?
if not you have to ask them to remove the flags or alter the properities
stopping you from another mdb

I believe it's Application.SetOption("Use Access Special Keys")=True
or db.properties("AllowSpecialKeys") = True
for the shift key
db.properties("AllowBypassKey") = true

But i think there's an example at www.mvps.org/access

hth

Pieter

 

[Guest]

Thanks... Yes, I can open it using ctl+g.

Last question: I read an access article that discussed custom menu. The
"tools-startup" option can be used to switch back to original access menu.
Here, there's are no such options in tools menu item. The only options left
in tools are "spelling" and "compact and repair database". The developer who
designed this application is no longer working. This is the only copy they
provided me.

 

[Guest]

Thanks... Yes, I can open it using ctl+g.

Last question: I read an access article that discussed custom menu. The
"tools-startup" option can be used to switch back to original access menu.
Here, there's are no such options in tools menu item. The only options left
in tools are "spelling" and "compact and repair database". The developer who
designed this application is no longer working. This is the only copy they
provided me.

 

[Albert D.Kallal]

The shift key allows you to by-pass the startup options.

IF they are not being used, then I guess you don't have a problem, or some
other issue is at stake

Here, there's are no such options in tools menu item. The only options
left
in tools are "spelling" and "compact and repair database". The developer
who
designed this application is no longer working. This is the only copy they
provided me.

That don't sound right. As mentioned, I would simply create a blank
database, and then import everhting.

Of course, during development, you will hold down the shift key so your
startup settings don't run. You then develop for awhile, and then to test in
"user" mode, you exit..and then re-enter the application without the shift
key bypassed. You will likely do this dance all day long as you run/test as
user mode, and then flip back in to developer mode (shift key used..so you
don't get the main custom menu). So, you can't develop, or really modify
things when you run your application with the startup settings...so you must
shift-by-pass them when you want to work.

And, in fact, I use alt-f4 to exit the application...the mdb file should
still be highlighted in the windows explore..so, then you hit enter key
(and, hold down shift key if you need be). This key stroke sequence and
exiting and re-entering the application will occur CONSTANTLY all day long
when you are developing.

When you finally have things just right...you create the mde
you plan to distribute...

It is likely that the shift key system is still in place. Did you try my
shift key utility?

 

[Albert D.Kallal]

The shift key allows you to by-pass the startup options.

IF they are not being used, then I guess you don't have a problem, or some
other issue is at stake

Here, there's are no such options in tools menu item. The only options
left
in tools are "spelling" and "compact and repair database". The developer
who
designed this application is no longer working. This is the only copy they
provided me.

That don't sound right. As mentioned, I would simply create a blank
database, and then import everhting.

Of course, during development, you will hold down the shift key so your
startup settings don't run. You then develop for awhile, and then to test in
"user" mode, you exit..and then re-enter the application without the shift
key bypassed. You will likely do this dance all day long as you run/test as
user mode, and then flip back in to developer mode (shift key used..so you
don't get the main custom menu). So, you can't develop, or really modify
things when you run your application with the startup settings...so you must
shift-by-pass them when you want to work.

And, in fact, I use alt-f4 to exit the application...the mdb file should
still be highlighted in the windows explore..so, then you hit enter key
(and, hold down shift key if you need be). This key stroke sequence and
exiting and re-entering the application will occur CONSTANTLY all day long
when you are developing.

When you finally have things just right...you create the mde
you plan to distribute...

It is likely that the shift key system is still in place. Did you try my
shift key utility?

 

[Guest]

Hello Mr Albert:

I used your application and enabled/disabled shiftkey bypass. Everyhtin
resulting in the same old problem. The application still displays those
custom menus. Whats worse is that the tools menu item doesn't show the "code"
option. This is a dead database. I tried importing the tables/forms into a
new database. The main form returns an error saying a custom toolbar from the
old database is missing. Don't know whats wrong here.

 

[Guest]

Hello Mr Albert:

I used your application and enabled/disabled shiftkey bypass. Everyhtin
resulting in the same old problem. The application still displays those
custom menus. Whats worse is that the tools menu item doesn't show the "code"
option. This is a dead database. I tried importing the tables/forms into a
new database. The main form returns an error saying a custom toolbar from the
old database is missing. Don't know whats wrong here.

 

[Pieter Wijnen]

make sure to select the advanced import options or Open the Form & Remove
the Custom Toolbar from it's properties

Pieter

resetting the toolbars to default should btw fix the problem

 

[Pieter Wijnen]

make sure to select the advanced import options or Open the Form & Remove
the Custom Toolbar from it's properties

Pieter

resetting the toolbars to default should btw fix the problem

 

[Guest]

Cool. This resolves my problem. Thank you both.

make sure to select the advanced import options or Open the Form & Remove
the Custom Toolbar from it's properties

Pieter

resetting the toolbars to default should btw fix the problem

 

[Guest]

Cool. This resolves my problem. Thank you both.

make sure to select the advanced import options or Open the Form & Remove
the Custom Toolbar from it's properties

Pieter

resetting the toolbars to default should btw fix the problem