deploying my database = overwhelmed.....

[rmulder]

I've got this nice little database that is now ready for use by our 10 or so office staff. i have been doing research on how best to deploy it. i have split it into a front end and a back end and put the back end on our server. i have referenced everything without drive letters. i was sure that i wanted to go the runtime route as while i could install access on all the computers, i'd rather not. so i downloaded the access developer resources and made a installer package that worked nicely except i didn't realize i would not have a office ribbon which i now know you have to create on which may be a bit difficult for me given my experience. I designed my db around using forms, queries, and reports for navigating so i mostly wanted the ribbon for doing some sorting, filtering, and few other basics. So, I'm wondering what you guys think the best route from here. I could install Access on all computers and customize the ribbon????? I've also been looking at autoupdaters for the front end namely here "http://www.btabdevelopment.com/main/AccessTools/tabid/78/Default.aspx" thanks for any and all input, you guys have been a great help in my journey so far!

 

[SOS]

The thing to remember when you use the Access Runtime is that you must provide Toolbars (prior to 2007) and Ribbons (2007 and on) for your application. You ALSO need to provide really good error handling or else you'll end up with unhandled errors which will cause the runtime to terminate.

 

[rmulder]

I'm not all too worried about errors as i did very little vba, but how do you "create" the ribbons. can someone with little to no programming experience handle it? do you lose any of the filtering, sorting capabilites? i really wanted the filter by form on the home ribbon in access.

 

[MSAccessRookie]

It may not seem like a big issue at first, but as SOS pointed Out, Error Handling is very important when you use Access Runtime. One thing to remember, is that a simple error can cause the program to stop running.

On occasion, users might create errors by Invalid Data Entry, and if any of these errors manages to get stored, then the program might not be able to recover until the data error is repaired.

 

[rmulder]

okay, so you guys think i should stick with installing access 2007 on all computers? customizing the ribbon to protect it from stupid people? password protect? accde? i also liked the idea of the runtime b/c it seemed more secure really limiting the users ability to screw stuff up.

 

[MSAccessRookie]

My apologies if I came off as being pushy. I actually have no opinion as to what you should do, I was only trying to support the point made by a previous poster. I also have no preference myself, but my company has Access installed on the Workstations for each user, and most of them are running multiple Access Applications.

 

[SOS]

There's nothing wrong with using the Runtime. In fact it is pretty good. But you have to create your own Ribbons and assign them and you have to include good error handling. So, take care of those and you'll be fine running the Access Runtime.

 

[MSAccessRookie]

There's nothing wrong with using the Runtime. In fact it is pretty good. But you have to create your own Ribbons and assign them and you have to include good error handling. So, take care of those and you'll be fine running the Access Runtime.

I agree entirely. I was only pointing out that if the OP did not include the necessary error handling, they might experience regrets at a future date.

 

[rmulder]

i don't know how to properly error handle (could prob learn) so I'm sticking with installing access on all computers and locking it down to the best of my abilities. Thanks everyone!

 

[SOS]

Well, good luck with it. You might, when you get a chance, check out this tutorial on Error Handling.

 

[Galaxiom]

You should use error handling in any design even if it runs on Access. Otherwise you just get dumb error messages and the procedure stops. You really should be looking at controlling what happens in unexpected circumstances.

Error handling is not so complicated to learn. Download MZ-Tools. It has an automated tool for inserting error handling with one click. You will need to understand the basic principles of Error handling to use it properly because the default is not quite perfect.

Locking it down in Access is probably just as hard to learn as error handling.

Also seems a very expensive option to install Access on every PC when the runtime is free.

I avoid ribbons and menus entirely by using buttons on the forms.

 

[gemma-the-husky]

The error handling is only part of it (although it is an important consideration in its own right)

My personal view is this

if you have MS office, i think the A2007 upgrade costs about £80.

The benefits you get of having full access is that all the toolbar icons are available - eg the A-Z sorts, the filter buttons etc. With the run time you have to provide all these yourself.

OK for ten users, this costs close to £1000 - but if you want to use Access in your business. and you obviously have at least 10 employees, then this seems a fairly modest cost for the benefits you get.

For the same reason, you could use open office, or some free or less expensive solution that MS Office - but I bet you don't

 

[rmulder]

umm, so i've been working on creating a custom ribbon with xml and im finding some commands just won't translate. like filter by form. i can get it to show but clicking on it does nothing. also, i wanted to add the close window button which cl,oses the active window whatever it is. but i add it and it will not show up. here's a snippet of my code..

<tab id="dbHomeTab" label="Home" visible="true">
<group id="dbHome1Group" label="Navigation">
<button id="Go_Home" label="Home Page" onAction="basic_open_forms.home"/>
<control idMso="WindowClose" label="Close" enabled="true"/>
</group>

I have lots of others working so I'm fairly sure my syntax is good. if this command is unavailab le does anyone know the vba code to close the active window? thanks!!!!!

 

[vbaInet]

<control idMso="WindowClose" label="Close" enabled="true"/>
</group>

That idMso should be a button I think.

<control idMso="WindowClose" label="Close" enabled="true"/>
</group>

You haven't closed your tab

If you haven't set this then any additions will not be reflected.
<ribbon startFromScratch="true">

Here are some good resources:
http://www.accessribbon.de/en/
http://msdn.microsoft.com/en-us/library/aa338202.aspx

 

[rmulder]

alright here's my whole code

<customUI xmlns="http://schemas.microsoft.com/office/2006/01/customui">
<ribbon startFromScratch="false">
<tabs>
<tab id="dbHomeTab" label="Home" visible="true">
<group id="dbHome1Group" label="Navigation">
<button id="Go_Home" label="Home Page" onAction="basic_open_forms.home"/>
<button idMso="WindowClose" label="Close" enabled="true"/>
</group>
<group id="dbHome2Group" label="Print">
<control idMso="PrintDialogAccess" label="Print" enabled="true"/>
<control idMso="FilePrintPreview" label="Print Preview" enabled="true"/>
</group>
<group id="dbHome3Group" label="Records">
<control idMso="DataRefreshAll" label="Refresh All" enabled="true"/>
<control idMso="GoToNewRecord" label="New" enabled="true"/>
<control idMso="RecordsSaveRecord" label="Save" enabled="true"/>
<control idMso="Delete" label="Delete" enabled="true"/>
</group>
<group id="dbHome4Group" label="Sort and Filter">
<control idMso="SortUp" label="Sort AScending" enabled="true"/>
<control idMso="SortDown" label="Sort Descending" enabled="true"/>
<control idMso="SortRemoveAllSorts" label="Remove Sorts" enabled="true"/>
<control idMso="FiltersMenu" label="Filter" enabled="true"/>
<control idMso="FilterBySelection" label="Selection" enabled="true"/>
<control idMso="FilterAdvancedMenu" label="Advanced" enabled="true"/>
<control idMso="FilterToggleFilter" label="Toggle Filter" enabled="true"/>
<control idMso="WindowClose" label="Close" enabled="true"/>
</group>
</tab>
</tabs>
</ribbon>
</customUI>

and a snapshot showing what i got for a menu...

 

[vbaInet]

Your screenshot is too tiny to read. What isn't showing?

 

[rmulder]

a google search brought me here http://www.utteraccess.com/forum/index.php?showtopic=1904722. a commands section at the top may be the answer??? i would assume u'd need a control section and a entry in the group section to add it to the ribbon. or is it just not possible to add this command in run-time??? your resources were good vbaInet but still not seeing the solution. thanks everyone!

 

[rmulder]

there should be a button below home page to close the current window. i used <button idMso="WindowClose" label="Close" enabled="true"/> and it's not showing. this button does exactly what i want when i add it to the QAT in full Access. so i wanted it in run-time.

 

[vbaInet]

What kind of button is it? If you use a button where it's a toggle button or a split button it won't be displayed.

The commands section is for redirecting the actions of the built-in commands.

Also, try this:

<button idMso="WindowClose" label="Close" enabled="true" visible="true" insertAfterMso="FilterToggleFilter" />

Are you sure WindowClose is the right idMso?

 

[rmulder]

finally got it to work! yaaaa. the visible = "true" was the key. why it was idk but it was. how come i don't need that for the rest of my controls and button that refers to a module? any insight on why? thanks vbaInet for your continued help, greatly appreciated!