access for others

[DeanLinCPR]

I am running Access 2k--as part of Office 2k pro. I work in a church
leadership and am designinga database to help us manage the day to day of the
congregation. we all have laptops but not all have access. Is there a way
to put it on a server without access and let them all beable to use it even
w/o having to buy access?

 

[John W. Vinson]

I am running Access 2k--as part of Office 2k pro. I work in a church
leadership and am designinga database to help us manage the day to day of the
congregation. we all have laptops but not all have access. Is there a way
to put it on a server without access and let them all beable to use it even
w/o having to buy access?

Well... only partially. You will need to purchase the appropriate "Runtime"
license; there are different way sto do this depending on version. See
http://www.granite.ab.ca/access/developereditionfaq.htm for details.

This might be one reason to upgrade to 2007 - the runtime is free. The
Developer's Edition for 2000 (if it's still available at all, that's four
generations back) was pretty pricey.

 

[Clifford Bass]

Hi,

The Access 2007 runtime is free to download from Microsoft
(http://www.microsoft.com/downloads/...D9-9DC6-4B38-9FA6-2C745A175AED&displaylang=en) and can open/use older database versions.

Clifford Bass

 

[John W. Vinson]

Hi,

The Access 2007 runtime is free to download from Microsoft
(http://www.microsoft.com/downloads/...D9-9DC6-4B38-9FA6-2C745A175AED&displaylang=en) and can open/use older database versions.

That's what I said, Clifford:

You'll need to develop the app in 2007 full version in order to use it with
the runtime, though, I'm pretty sure.

 

[Clifford Bass]

Hi John,

Actually, what you wrote and what I wrote were slightly different. You
were saying he had to upgrade. I was saying he did not. However, since I
don't always double-check something before I post, I did a quick test. On a
machine with Office 2003 and Access 2007 Runtime (Office 2007 never
installled) I was able to do this:

Create a 2003 database with a table and a form. Converted it to Access
97. Yes, I know he did not specify as old as 97, but I was curious. Opened
it and added a record using the Access 2007 Runtime. Interestingly, the
runtime asked / recommended I convert the database. I chose not to the first
time. The second time I chose to do so, and it converted it to a 2007
database, with an "error" about Access 2007 databases no longer supporting
user-level security. Opening a 2000 or later database does not seem to
invoke the prompting to convert.

One annoying thing that I have not attempted to deal with: When you
jump back and forth between Access 2003 and Access 2007 Runtime, they both go
through their "installing" process.

Clifford Bass

 

[John W. Vinson]

Create a 2003 database with a table and a form. Converted it to Access
97. Yes, I know he did not specify as old as 97, but I was curious. Opened
it and added a record using the Access 2007 Runtime.

VERRY interesting. I'm glad to know that!

One annoying thing that I have not attempted to deal with: When you
jump back and forth between Access 2003 and Access 2007 Runtime, they both go
through their "installing" process.

One reason I've been putting off installing 2007. Need to get that done soon
though... once I get my second machine rebuilt.

Thanks for the correction, Clifford!

 

[Clifford Bass]

You are welcome John!

Clifford Bass

VERRY interesting. I'm glad to know that!


One reason I've been putting off installing 2007. Need to get that done soon
though... once I get my second machine rebuilt.

Thanks for the correction, Clifford!

 

[AccessVandal via AccessMonster.com]

Yes, users can install Access2007 runtime. You can use Access2000 to deploy
your application.

1. You’ll need to edit the users registry to enable the macro warning message.

2. Do not use ActiveX.
3. Do note of windows updates as sometimes it can cause problems.
4. Or use Access2007 with Developer Extension to deploy on a secure/trusted
location.

Usually there’s no problem with a machine on windows xp and A2K7 runtime,
sometimes windows update can cause problem, which I had decovered. All you
need to do is just recompile, compact and repair, make the mde again or
sometime a little code change does wonders.

However, if the users are using Vista, you may need to do more work. On my
early deployment, I did not encounter problems until vista updates. Example,
it will failed to read a filter condition like

ItemID Like Ԡ& Me.ItemID & “*’â€

It will read text like “ACCExxxâ€, “ACCBxxx†but not “ACCSxxxâ€. This problem
varies, sometimes it can sometime it can’t. Or it simply failed to read a
control value.

To avoid these errors, make sure you have proper error handling to trap where
the errors came from. Like..

MsgBox “Error No: “ & Err.Number & “ – “ & Err.Description , “VbCriticalâ€,
“TitleWhereEventFailedNamedâ€

Hope this will help.