The record source...specified on this form or report does not exis

Ought to add - somebody else has suggested I should do away with the split
between the databases and simply migrate the back end tables into the front
end database. Apparantly this could be part of the problem.

I always thought that the split was "the right way to do things" and reduced
the chances of corruption etc, but to be honest I would welcome some pointers.

The database only has a few users and backend plus front end comes to about
15MB, the bulk of the data being in the warehouse.

Thoughts?


"Fred" wrote:

The developers in these forums all say never use in-table lookups, and to do
data entry only through forms. While I suspect that for us mere mortals,
breaking that rule is sometimes a good idea, I think that yours is an
example where the lookups are better off being created in the forms rather
than the tables.

I think that you will get different answers from different groups. Most of
the top level experts in these forums are developers or do heavy-duty
development work. They have to deal in deploying and maintaining
applications for larger amounts of users. including those who know zero about
Access, or those who like to mess with stuff and do damage, and just blame
the developer when they mess something up. And so they also have to make
stuff dummyproof and bulletproof. That environment calls for splitting
all databases, having users interface only through forms, never using
in-table lookups etc.

My day job is running smaller technical companies, 25 employees, 10 users
on any given database, 4 simultaneous users on any DB. I've got it
eaasier than the developers because I have fewer users, and they all know
Access a little, 1/2 of them are engineers, and all work for me and know the
rules. Our folks often create little databases in minutes instead of Word
and Excel documents. They do 1/4 of their data entry and 3/4 of their
searching in queries rather than forms, including specifying never-planned
search, sort and view conditions in the query grid in seconds. And since
(I think) that in-table dropdowns are the only way to have dropdowns in
queries, we use some of those. . Conversely, the development time for a DB
has to be 10 minutes or 10 hours and not 100 / 500 hours Only our most
widely used databases are split.


So there's two sides on the Access universe.

Indeed. I learned some years ago to be very careful who I debated database
philosophy with!

"Fred" wrote:

I think that you will get different answers from different groups. Most of
the top level experts in these forums are developers or do heavy-duty
development work. They have to deal in deploying and maintaining
applications for larger amounts of users. including those who know zero about
Access, or those who like to mess with stuff and do damage, and just blame
the developer when they mess something up. And so they also have to make
stuff dummyproof and bulletproof. That environment calls for splitting
all databases, having users interface only through forms, never using
in-table lookups etc.

My day job is running smaller technical companies, 25 employees, 10 users
on any given database, 4 simultaneous users on any DB. I've got it
eaasier than the developers because I have fewer users, and they all know
Access a little, 1/2 of them are engineers, and all work for me and know the
rules. Our folks often create little databases in minutes instead of Word
and Excel documents. They do 1/4 of their data entry and 3/4 of their
searching in queries rather than forms, including specifying never-planned
search, sort and view conditions in the query grid in seconds. And since
(I think) that in-table dropdowns are the only way to have dropdowns in
queries, we use some of those. . Conversely, the development time for a DB
has to be 10 minutes or 10 hours and not 100 / 500 hours Only our most
widely used databases are split.


So there's two sides on the Access universe.

Well something has changed in the frontend. Does the frontend still
include a link to the the[List - Current] table?

Joan Wild
MS Access MVP


mr-tom wrote:
Yep - there is a lookup, but it works in the back end, it always used to work
in the front end and nothing there has been changed.

Anything else I can try?

"Joan Wild" wrote:

Since you get the message referring to[List - Current] when you open
[Data - Advisers], then there is something in the properties of Data -
Advisers.

My first guess would be that there is a lookup defined in Data -
Advisers on some field.

Joan Wild
MS Access MVP


mr-tom wrote:
Hello,

I've got what I'm really hoping isn't a big problem, but I have a nasty
feeling about this.

I have a database which functions as a front end for an SQL Server
warehouse, so it just holds linked tables and queries.

I have another database (let's call it the back end database) which holds
data which the SQL server warehouse doesn't and is also linked to by the
front end database.

A huge amount of work is invested in these and replacing them is a complete
non-starter so I have to solve this problem.

When I open one of the linked tables (called Data - Advisers) in the front
end database, I get the following message:

The record source 'SELECT[List - Current].[Current Ref],[List -
Current].Current FROM[List - Current];' specified on this form or report
does not exist.
You misspelled the name or it was renames or deleted in the current
database, or it exists in a different database...

Nothing has been deleted or renamed. Nothing has been changed at all.
Going into the back end database, everything is present and correct, no error
messages.

This has worked fine for ages - no errors before now.

I've compacted and repaired both databases. I've also turned off the Name
Autocorrect in the front end database and re-compacted (I saw somewhere that
this could help) and repaired but to no avail.

I don't know what could have cuased this or how to fix it. Unfortunately,
google hasn't offered much help. ;-)

Any help or pointers you can provide will be greatly appreciated.

Good thought.

Yes - it's still linked and displays correctly without any error messages etc.

I'm restoring from backup and keeping my fingers crossed.

Also looking at whether I can track changes to field names, designs etc.

Tom.

"Joan Wild" wrote:

Well something has changed in the frontend. Does the frontend still
include a link to the the[List - Current] table?

Joan Wild
MS Access MVP


mr-tom wrote:
Yep - there is a lookup, but it works in the back end, it always used to work
in the front end and nothing there has been changed.

Anything else I can try?

"Joan Wild" wrote:

Since you get the message referring to[List - Current] when you open
[Data - Advisers], then there is something in the properties of Data -
Advisers.

My first guess would be that there is a lookup defined in Data -
Advisers on some field.

Joan Wild
MS Access MVP


mr-tom wrote:
Hello,

I've got what I'm really hoping isn't a big problem, but I have a nasty
feeling about this.

I have a database which functions as a front end for an SQL Server
warehouse, so it just holds linked tables and queries.

I have another database (let's call it the back end database) which holds
data which the SQL server warehouse doesn't and is also linked to by the
front end database.

A huge amount of work is invested in these and replacing them is a complete
non-starter so I have to solve this problem.

When I open one of the linked tables (called Data - Advisers) in the front
end database, I get the following message:

The record source 'SELECT[List - Current].[Current Ref],[List -
Current].Current FROM[List - Current];' specified on this form or report
does not exist.
You misspelled the name or it was renames or deleted in the current
database, or it exists in a different database...

Nothing has been deleted or renamed. Nothing has been changed at all.
Going into the back end database, everything is present and correct, no error
messages.

This has worked fine for ages - no errors before now.

I've compacted and repaired both databases. I've also turned off the Name
Autocorrect in the front end database and re-compacted (I saw somewhere that
this could help) and repaired but to no avail.

I don't know what could have cuased this or how to fix it. Unfortunately,
google hasn't offered much help. ;-)

Any help or pointers you can provide will be greatly appreciated.