i had done database in 2007, when i try to convert to 2003, the message
appear that "feuture in current file format...are nt support by early
version".
doyou have any idea how to solve this problem. /i try to avoid from removing
this function.

The message "feature in current file format is not supported by early
versions" means that the function you have used will not work in early
versions.

The solution to the problem would seem to be one of the following:

a) Removing the Access 2007 specifici function
b) Finding an alternative function that will work in Access 2007 as well as
Access 2003
c) Not converting the database.


"apasaja" <(E-Mail Removed)> wrote in message
news:816D8485-5627-4A4D-B8D7-(E-Mail Removed)...
>i had done database in 2007, when i try to convert to 2003, the message
> appear that "feuture in current file format...are nt support by early
> version".
> doyou have any idea how to solve this problem. /i try to avoid from
> removing
> this function.

Apasaga,

Further to George's comments, I would say it is a wise approach to always
create/develop a database in the earliest version of Access that you will
want to use it in.

--
Steve Schapel, Microsoft Access MVP


"apasaja" <(E-Mail Removed)> wrote in message
news:816D8485-5627-4A4D-B8D7-(E-Mail Removed)...
> i had done database in 2007, when i try to convert to 2003, the message
> appear that "feuture in current file format...are nt support by early
> version".
> doyou have any idea how to solve this problem. /i try to avoid from
> removing
> this function.

Thanks for the pickup Steve. One of the more obvious suggestions and I
overlooked it.

"Steve Schapel" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Apasaga,
>
> Further to George's comments, I would say it is a wise approach to always
> create/develop a database in the earliest version of Access that you will
> want to use it in.
>
> --
> Steve Schapel, Microsoft Access MVP
>
>
> "apasaja" <(E-Mail Removed)> wrote in message
> news:816D8485-5627-4A4D-B8D7-(E-Mail Removed)...
>> i had done database in 2007, when i try to convert to 2003, the message
>> appear that "feuture in current file format...are nt support by early
>> version".
>> doyou have any idea how to solve this problem. /i try to avoid from
>> removing
>> this function.
>

"Steve Schapel" <(E-Mail Removed)> wrote:

>Further to George's comments, I would say it is a wise approach to always
>create/develop a database in the earliest version of Access that you will
>want to use it in.

I, somewhat, disagree. I work on my Granite Fleet Manager in A2003
but create the MDE in A2000. The runtime is in A2003. I still have a
few clients using A2000 so I want to leave it in that format. There
is no pressing reason to use any A2003 specific functionality as any
new functionality was quite limited.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

"Tony Toews [MVP]" <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

> "Steve Schapel" <(E-Mail Removed)> wrote:
>
>>Further to George's comments, I would say it is a wise approach to
>>always create/develop a database in the earliest version of Access
>>that you will want to use it in.
>
> I, somewhat, disagree. I work on my Granite Fleet Manager in
> A2003 but create the MDE in A2000. The runtime is in A2003. I
> still have a few clients using A2000 so I want to leave it in that
> format. There is no pressing reason to use any A2003 specific
> functionality as any new functionality was quite limited.

What you describe is actually what I interpreted Steve as meaning --
he said "earliest version of Access" but I read it as "earliest file
format." It's very likely I was reading more into his comment than
was there, but I read it as being exactly what you describe: you use
A2000 format (you couldn't create an A2000 MDE if you weren't using
A2000 format) and develop in A2003. That's exactly how I do all my
work.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/