Filtering problem - reposted, still need help

  • Thread starter alecwood via AccessMonster.com
  • Start date
A

alecwood via AccessMonster.com

Hi All

I've been asking this on lots of forums but noone answers :(

I wonder if someone can assist me. I've got an inherited access database
which for the most part uses bound forms (about 40 of them) to an access
back-end. Database is in continuous use by around 10 clients. I am not very
experienced with databases, but with a big pile of books I am learning.

We have a need to make some of the data accessible to customers outside, so
on the advise of various in the know people I have upsized to an Access
Project which will allegedly make things more reliable, and make presenting
data by internet easier, as well as coping with an expected surge in data
volume, but now my Access frontend (.adp) is broken

The crux of my problem is that I had used the following on-click event, or a
very similar one, in most of my forms to search the database
DoCmd.ApplyFilter "",
"[t_MainData]![nAmk_ID]=[Forms]![frmPreInsp]![SearchDetails]"

This doesn't work and gives me an error "Run-time error '30100'; Cannot
apply Filter on one or more fields specified in the Filter property."

I have searched these forums, all my books, google, microsoft.com etc
without success.

Can anyone help point me in the right direction?
 
B

BMore via AccessMonster.com

With the info you are giving, it is hard to find the problem.
There is a workaround though:
Make a query that selects the data you want and set it as recordsource on a
form for these clients. (The criteria for that query may come from a form or
formula)

Hope this helps,
Ben
Hi All

I've been asking this on lots of forums but noone answers :(

I wonder if someone can assist me. I've got an inherited access database
which for the most part uses bound forms (about 40 of them) to an access
back-end. Database is in continuous use by around 10 clients. I am not very
experienced with databases, but with a big pile of books I am learning.

We have a need to make some of the data accessible to customers outside, so
on the advise of various in the know people I have upsized to an Access
Project which will allegedly make things more reliable, and make presenting
data by internet easier, as well as coping with an expected surge in data
volume, but now my Access frontend (.adp) is broken

The crux of my problem is that I had used the following on-click event, or a
very similar one, in most of my forms to search the database
DoCmd.ApplyFilter "",
"[t_MainData]![nAmk_ID]=[Forms]![frmPreInsp]![SearchDetails]"

This doesn't work and gives me an error "Run-time error '30100'; Cannot
apply Filter on one or more fields specified in the Filter property."

I have searched these forums, all my books, google, microsoft.com etc
without success.

Can anyone help point me in the right direction?
 
A

Arvin Meyer [MVP]

First, you say that you are running an Access front-end to an Access
back-end. Then you add that this is an ADP. ADP back-ends are SQL-Server,
not Access/Jet. Once we've settle that, we can go on, because that may
change the way we do a search. Also, you need to supply a bit more code and
information from the error so we can see why the error is occuring..
 
A

alecwood via AccessMonster.com

Sorry, I guess I wasn't clear enough

It was Access front end and back end, split database, two .mdb files. In all
cases the forms were bound to tables or queries as very basic access
databases written by noobs tend to be LOL.

Following advice I upscaled, so now I have an ADP front end and the upscaled
tables on an instance of SQL server.

I used the upsizing wizard to do the job, corrected the problems it found and
now I can see and add records, but my previously working search functions
just don't.

I'm just trying to find an alternative to shore it up in the interim. I
appreciate what I want is unbound forms, disconnected databases and good VBA
code running behind them, but I don't want to sit up until midnight every
night with a laptop to get it done, which is what it would take at my level
of knowledge.

If I can shore it up with a temp solution then I can recode properly at
leisure, and hopefully do a better job.

Alec
First, you say that you are running an Access front-end to an Access
back-end. Then you add that this is an ADP. ADP back-ends are SQL-Server,
not Access/Jet. Once we've settle that, we can go on, because that may
change the way we do a search. Also, you need to supply a bit more code and
information from the error so we can see why the error is occuring..
[quoted text clipped - 27 lines]
Can anyone help point me in the right direction?
 
A

alecwood via AccessMonster.com

"Disconnected databases" LOL, sorry I meant recordsets.......


Sorry, I guess I wasn't clear enough

It was Access front end and back end, split database, two .mdb files. In all
cases the forms were bound to tables or queries as very basic access
databases written by noobs tend to be LOL.

Following advice I upscaled, so now I have an ADP front end and the upscaled
tables on an instance of SQL server.

I used the upsizing wizard to do the job, corrected the problems it found and
now I can see and add records, but my previously working search functions
just don't.

I'm just trying to find an alternative to shore it up in the interim. I
appreciate what I want is unbound forms, disconnected databases and good VBA
code running behind them, but I don't want to sit up until midnight every
night with a laptop to get it done, which is what it would take at my level
of knowledge.

If I can shore it up with a temp solution then I can recode properly at
leisure, and hopefully do a better job.

Alec
First, you say that you are running an Access front-end to an Access
back-end. Then you add that this is an ADP. ADP back-ends are SQL-Server,
[quoted text clipped - 6 lines]
 
H

Hooker DBA [MSFT]

Arvin should not be trusted; he believes that the only appropriate use
of Access is to use MDB / MDE files.

I mean.. that cry baby needs to lose the training wheels



First, you say that you are running an Access front-end to an Access
back-end. Then you add that this is an ADP. ADP back-ends are SQL-Server,
not Access/Jet. Once we've settle that, we can go on, because that may
change the way we do a search. Also, you need to supply a bit more code and
information from the error so we can see why the error is occuring..
--
Arvin Meyer, MCP, MVPhttp://www.datastrat.comhttp://www.mvps.org/accesshttp://www.accessmvp.com



I've been asking this on lots of forums but noone answers :(
I wonder if someone can assist me. I've got an inherited access database
which for the most part uses bound forms (about 40 of them) to an access
back-end. Database is in continuous use by around 10 clients. I am not
very
experienced with databases, but with a big pile of books I am learning.
We have a need to make some of the data accessible to customers outside,
so
on the advise of various in the know people I have upsized to an Access
Project which will allegedly make things more reliable, and make
presenting
data by internet easier, as well as coping with an expected surge in data
volume, but now my Access frontend (.adp) is broken
The crux of my problem is that I had used the following on-click event, or
a
very similar one, in most of my forms to search the database
DoCmd.ApplyFilter "",
"[t_MainData]![nAmk_ID]=[Forms]![frmPreInsp]![SearchDetails]"
This doesn't work and gives me an error "Run-time error '30100'; Cannot
apply Filter on one or more fields specified in the Filter property."
I have searched these forums, all my books, google, microsoft.com etc
without success.
Can anyone help point me in the right direction?

- Show quoted text -
 
A

Arvin Meyer [MVP]

If you wrote your original search functions in DAO, you are out of luck.
You'll need to rewrite them in ADO. Sorry no shortcuts.

Just for your edification, Microsoft now recommends using MDBs (and
presumably DAO) when accessing SQL-Server data. ADPs will still work, and
should for some time, but they will not be making and upgrades for them. ADO
has been replaced by ADO.NET and I expect it will go the way of RDO.

The advice to upscale may have been premature. There are certainly some real
advantages to using a SQL-Server back-end, but sometimes a VW is better
suited to a task than an 18 wheeler.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

alecwood via AccessMonster.com said:
"Disconnected databases" LOL, sorry I meant recordsets.......


Sorry, I guess I wasn't clear enough

It was Access front end and back end, split database, two .mdb files. In
all
cases the forms were bound to tables or queries as very basic access
databases written by noobs tend to be LOL.

Following advice I upscaled, so now I have an ADP front end and the
upscaled
tables on an instance of SQL server.

I used the upsizing wizard to do the job, corrected the problems it found
and
now I can see and add records, but my previously working search functions
just don't.

I'm just trying to find an alternative to shore it up in the interim. I
appreciate what I want is unbound forms, disconnected databases and good
VBA
code running behind them, but I don't want to sit up until midnight every
night with a laptop to get it done, which is what it would take at my
level
of knowledge.

If I can shore it up with a temp solution then I can recode properly at
leisure, and hopefully do a better job.

Alec
First, you say that you are running an Access front-end to an Access
back-end. Then you add that this is an ADP. ADP back-ends are SQL-Server,
[quoted text clipped - 6 lines]
Can anyone help point me in the right direction?
 
T

Todos Menos [MSFT]

Arvin

you are not speaking the full truth

what about reports?

why would reports run 'considerably faster in adp' but forms won't?

ADP won the war, MDB is for mother fucking losers and retards that
can't learn a real db





If you wrote your original search functions in DAO, you are out of luck.
You'll need to rewrite them in ADO. Sorry no shortcuts.

Just for your edification, Microsoft now recommends using MDBs (and
presumably DAO) when accessing SQL-Server data. ADPs will still work, and
should for some time, but they will not be making and upgrades for them. ADO
has been replaced by ADO.NET and I expect it will go the way of RDO.

The advice to upscale may have been premature. There are certainly some real
advantages to using a SQL-Server back-end, but sometimes a VW is better
suited to a task than an 18 wheeler.
--
Arvin Meyer, MCP, MVPhttp://www.datastrat.comhttp://www.mvps.org/accesshttp://www.accessmvp.com

alecwood via AccessMonster.com said:
"Disconnected databases" LOL, sorry I meant recordsets.......
alecwood said:
Sorry, I guess I wasn't clear enough
It was Access front end and back end, split database, two .mdb files. In
all
cases the forms were bound to tables or queries as very basic access
databases written by noobs tend to be LOL.
Following advice I upscaled, so now I have an ADP front end and the
upscaled
tables on an instance of SQL server.
I used the upsizing wizard to do the job, corrected the problems it found
and
now I can see and add records, but my previously working search functions
just don't.
I'm just trying to find an alternative to shore it up in the interim. I
appreciate what I want is unbound forms, disconnected databases and good
VBA
code running behind them, but I don't want to sit up until midnight every
night with a laptop to get it done, which is what it would take at my
level
of knowledge.
If I can shore it up with a temp solution then I can recode properly at
leisure, and hopefully do a better job.
Alec
First, you say that you are running an Access front-end to an Access
back-end. Then you add that this is an ADP. ADP back-ends are SQL-Server,
[quoted text clipped - 6 lines]
Can anyone help point me in the right direction?
 
T

Todos Menos [MSFT]

my 18 wheeler is better, more nimble, better mileage and easier to
drive than your MDB _CRAP_

stick a mother fucking cork in it RETARD





If you wrote your original search functions in DAO, you are out of luck.
You'll need to rewrite them in ADO. Sorry no shortcuts.

Just for your edification, Microsoft now recommends using MDBs (and
presumably DAO) when accessing SQL-Server data. ADPs will still work, and
should for some time, but they will not be making and upgrades for them. ADO
has been replaced by ADO.NET and I expect it will go the way of RDO.

The advice to upscale may have been premature. There are certainly some real
advantages to using a SQL-Server back-end, but sometimes a VW is better
suited to a task than an 18 wheeler.
--
Arvin Meyer, MCP, MVPhttp://www.datastrat.comhttp://www.mvps.org/accesshttp://www.accessmvp.com

alecwood via AccessMonster.com said:
"Disconnected databases" LOL, sorry I meant recordsets.......
alecwood said:
Sorry, I guess I wasn't clear enough
It was Access front end and back end, split database, two .mdb files. In
all
cases the forms were bound to tables or queries as very basic access
databases written by noobs tend to be LOL.
Following advice I upscaled, so now I have an ADP front end and the
upscaled
tables on an instance of SQL server.
I used the upsizing wizard to do the job, corrected the problems it found
and
now I can see and add records, but my previously working search functions
just don't.
I'm just trying to find an alternative to shore it up in the interim. I
appreciate what I want is unbound forms, disconnected databases and good
VBA
code running behind them, but I don't want to sit up until midnight every
night with a laptop to get it done, which is what it would take at my
level
of knowledge.
If I can shore it up with a temp solution then I can recode properly at
leisure, and hopefully do a better job.
Alec
First, you say that you are running an Access front-end to an Access
back-end. Then you add that this is an ADP. ADP back-ends are SQL-Server,
[quoted text clipped - 6 lines]
Can anyone help point me in the right direction?
 
T

Todos Menos [MSFT]

Access MDB will not work for 10 users

instead of spending all your time linking and refresing and writing
connections strings-- stick around with ADP

and use WHERE clauses, not filters

ONLY LOAD THE RECORDS YOU NEED
 
T

Todos Menos [MSFT]

or if you MUST then try this

DoCmd.ApplyFilter "","nAmk_ID= " & [Forms]![frmPreInsp]!
[SearchDetails]


seriously

give that a shot, bro

HTH
don't listen to this Arvin Chipmunk he is a diseased fat lazy retard
that is stuck in the 80s
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top