access form 2007 to 2003

[abdul]

I have created a form in access 2007 but the form to be installed in msoffice 2003 system. When I am opening the form in 2003 some controls are not working. I saved the form save as 2003 form but still the problem continues. any suggestions. plz reply
Thank u
Abdul

 

[missinglinq]

...When I am opening the form in 2003 some controls are not working...

First suggestion, if you want our help, Abdul, would be that you give us a better explanation of your problem than simply saying some controls are not working!

What type of Controls are not working? What exactly are they not doing that you expect them to do?

Just as a general comment, it is always best policy, when developing for multiple versions of Access, especially pre-and-post 2007, to develop in the lowest version that is going to be used. Many new features were added in 2007/2010 that simply do not exist in previous versions.

Welcome to AWF!

Linq ;0)>

 

[Galaxiom]

Just as a general comment, it is always best policy, when developing for multiple versions of Access, especially pre-and-post 2007, to develop in the lowest version that is going to be used. Many new features were added in 2007/2010 that simply do not exist in previous versions.

There is nothing whatsoever in the 2007 format worth changing over from using a 2003 mdb format. Moreover the loss of the Trusted Document means the 2007 format is a dead donkey in many environments.

They added it back for 2010 along with a number of other features that *might* be worth considering. Reports as subforms is one. (Indeed when I started developing I was suprised it wasn't always included.) Derived fields ...bah, multivalue fields (also in 2007) ... bah.

However developing in 2010 can still lead to problems in 2007 systems because even though they both use accd* files, 2010 includes features unsuported in 2007.

As far as I can see, unless all users are on 2010, sticking to developing in mdb format is still the most sensible choice. It is versatile and works on most systems. In my experience they work flawlessly in the 2007 Runtime.

 

[missinglinq]

...As far as I can see, unless all users are on 2010, sticking to developing in mdb format is still the most sensible choice. It is versatile and works on most systems.

I agree, which is why I haven't so-called 'upgraded' from 2003! None of the 'added features,' in my opinion, in 2007/2010 seem worth the headaches that come with the versions!

Actually, about the only problem I have with not running 2007/2010 is the sometime inability to answers questions here and on other forums I frequent about those versions!

I really think that Access 2003 is going to be like Visual Basic 6. When VB.Net came our, everybody predicted that VB 6 would be caput in a year or two, but that simply hasn't happened! Apps written in VB6 are simply too reliable and too pervasive in American business for it to simply dry up and blow away!

Linq ;0)>