Access 2007 Database works in XP not in Vista

[sailinxtc]

Anybody have an idea where to start ?

my project was developed in access 2003 originally.

I then bought the 2007 and upgraded it so I could use the package manager.

The package also includes the access runtime that installs

Installs and works great in XP

Installs in Vista and partially works.

Problems are the calendar and date/time functions dont function in Vista

Not sure if its Vista or something within my database and VB etc...

Any pointers would be appreciated.

 

[boblarson]

If you have both Access 2007 and the runtime installed, I believe you will need to do this:

http://www.btabdevelopment.com/main...ista/RunasAdministrator/tabid/87/Default.aspx

 

[sailinxtc]

Sorry to confuse this, I installed the program on a Vista machine to bench test the database application. It does not have the full access 2007 program installed. It only has the runtime package installed on the Vista Machine, as did the Xp machine also that I bench tested it on.

 

[boblarson]

Did you set the Trusted Location in the Vista machine?

 

[sailinxtc]

Also the database and runtime opens and runs in the vista computer but some of the functions dont work as mentioned where the calendar should pop up allowing the user to select the month and day year etc.. .easily, and the date/time picker function also does not function.

 

[sailinxtc]

no i did not, i am not sure what that is?

 

[boblarson]

Normally you do this:
http://www.btabdevelopment.com/main...owtoenablecodeandmacros/tabid/57/Default.aspx

But with the runtime you need to modify the registry:

http://bytes.com/forum/post2752405-4.html

 

[sailinxtc]

I hope that does it, am I correct to assume this only needs to be done with Vista and the runtime since it works in Xp with the runtime ?

 

[boblarson]

actually, you need to set the trusted locations for Access 2007 on any operating system.

 

[sailinxtc]

Ok, so I must be doing that temporary when I click the options and enable it each time. I will try it tomorrow, I appreciate all the info! Thanks again!

 

[boblarson]

Ok, so I must be doing that temporary when I click the options and enable it each time. I will try it tomorrow, I appreciate all the info! Thanks again!

Yes, that is exactly what is happening.

 

[sailinxtc]

can you reference any sites on creating scripts for making the edits to the registry unattended that I can call out in package manager deployment

 

[sailinxtc]

I packaged a 2007 access runtime and it installs and runs fine on XP, Vista it will install and Run howerver My Date Time Picker (I think that is what it is called) doesn't have the option to open or click on it in Vista. I get no warning or security issues. Anyone have any idea's where to start ?

 

[amriasg]

Good day to all gentlemen and women

Who would like to congratulate me????? I found the group (forum) that I'm searching for.

Really I'm so glad

Thank you all for this kind of supporting and cooperation.

 

[sailinxtc]

Here was the fix for this, I know nothing about Vista for one.

I was told the ActiveX features of access 2003 are not supported in Vista.

Why when I installed the access 2007 and opened my database for the first time it didn't update it when I was asked not sure?

So basically none of the activeX date and/or time picker features from 2003 access work in Vista 32 bit version.

At least that is what I was told and had to change my database features to work another way.

Anybody have an idea where to start ?

my project was developed in access 2003 originally.

I then bought the 2007 and upgraded it so I could use the package manager.

The package also includes the access runtime that installs

Installs and works great in XP

Installs in Vista and partially works.

Problems are the calendar and date/time functions dont function in Vista

Not sure if its Vista or something within my database and VB etc...

Any pointers would be appreciated.

 

[boblarson]

Never heard of that before and I seriously doubt the validity of it. There is probably something else going on.

 

[sailinxtc]

Unfortunately I paid for the Microsoft Support incident, Worked with a gentlemen in India that seemed very fluent and knowledgeable on the access things. I specifically asked about a bug with Vista or access and both where denied.

WE bascically ended up calling the Date picker with another method other than the activeX control. Howerver I was not able to use the other activeX controls where a default time of 12:00 was inserted in the field and then used the activeX control with up/down arrow next to time to adjust it easily etc...

I am guessing there will be more of this seen but couldn't believe there was nothing out there on it if it where a problem?

Did you see my other posting issue ?

Never heard of that before and I seriously doubt the validity of it. There is probably something else going on.

 

[sailinxtc]

Have another question with the Access 2007 Package Manager and Runtime. Originally my database was started in 2003 and have worked with it in access 2007. The file extension has always remained a MDB or MDE. I started looking into compiling some of the modules and found that one should create the ACCDE from database tools etc... or save as.

I tried the convert method in 2007 from the MDB to the ACCDB but it would not work. I decided to try and create a new ACCDB and cut and paste everything from the MDB to the New ACCDB. All looked and works well within Access 2007.

Of course I made lots of edits and changes before trying to package and use the Runtime on a computer with just the runtime. Tried both the ACCDB and ACCDE with the package manager and runtime.

The Runtime opens but has nothing in it, or appears to have nothing.

What am I missing ?

 

[The_Doc_Man]

OK, first things first.

When Access runs, it has a pot-load of libraries that it brings with it. You don't always use all of them. Some things come with Office - like the VBA libraries. Some are specific to other applications, like the Excel and Word libraries. Some originate from other sources. It's all a crap-shoot as to what you have. Microsoft, in their somewhat less than infinite wisdom, updates the libraries now and then but doesn't always advise you in a clear-cut way.

You might therefore be missing some references related to the idea that you have been trying to use old .DLL or .OLB or .TLB files that don't exist on your system.

Another possibility is that references are retained in the registry, which is specific to each machine (and each O/S). You might have to just open up Access on your old system, open a module, follow menu item Tools >> References, and write down names of referenced libraries. (They'll have a check-mark.) Then try to open up the same pane and menu item and dialog box on the new system. Be sure you can check-mark each box. Some of the names will have changed in the transition from Ac2k3 to Ac2k7. It is inevitable. That could also be doing it.

Don't know how you would handle this for the Run-time stuff. I've never had the need to play with that feature.

 

[sailinxtc]

Narrowed it down a bit more....

I can open the .accde file in Access 2007 (non runtime version) and all works fine.

Installed just the runtime on the other machine, without using the package manager and opened the .accde file and get the following warning message:

Warning its not possible to determine that the content came from a trustworthy source. you should leave this content disabled unless the content provides critical functionality and you trust its source.

the file might contain unsafe content that could harm your computer, do you want to open the file or cancel the operation.

I click open to continue and get nothing, I can pick File pulldown and close database, but that is it.

Both computers are XP Pro and have all updates etc...

Normally my switchboard menu opens etc...