#ERROR

[Guest]

Access 2000
Split Front-end/Back-end

We had a field in our table incorrectly set as a number field rather than a
date field. So, if a user typed today's date, the number was stored as 38522
(I believe). We changed the field to a date field, and it was working okay.
Now, however, we are getting a #ERROR message, "Reserved error (-1517). There
is no message for this error."
How do we fix this?
Thanks,

 

[Joan Wild]

Access 2000
Split Front-end/Back-end

We had a field in our table incorrectly set as a number field rather than
a
date field. So, if a user typed today's date, the number was stored as
38522
(I believe).

That is how Access always stores a date (with a decimal portion as well for
the time as a portion of a day)

We changed the field to a date field, and it was working okay.
Now, however, we are getting a #ERROR message, "Reserved error (-1517).
There
is no message for this error."

This error will occur if you change the design of a table, but don't follow
through with a compact. Since you have a split database, it is a good idea
to compact the backend after a design change, and also refresh the links in
the frontend and compact it.

 

[Guest]

--
Howard

That is how Access always stores a date (with a decimal portion as well for
the time as a portion of a day)


This error will occur if you change the design of a table, but don't follow
through with a compact. Since you have a split database, it is a good idea
to compact the backend after a design change, and also refresh the links in
the frontend and compact it.


--
Joan Wild
Microsoft Access MVP

Joan:

That did it. Thanks!
Another question. The back-end of our database is on the share drive and the
front-end on each users c: drive. Would it work if the front and back ends
are both on the share drive?
The database is about 20,000 records and used by 35 or so people to track
tax returns, mainly during Tax Season. Before splitting the database we had
problems, but since then it's run smoothly. I'm reluctant to change anything!
Howard

 

[Joan Wild]

That did it. Thanks!

You're welcome.

Another question. The back-end of our database is on the share drive and
the
front-end on each users c: drive. Would it work if the front and back ends
are both on the share drive?

The way you have it set up now is the preferred way. Having multiple users
using the same frontend will lead to corruption. If you are asking this
because you face updating all 35 users with a new/modified frontend, you'll
want to look at a way to automate this. You could use a simple batch file
or look at Tony Toews' AutoFE Updater at
http://www.granite.ab.ca/access/autofe.htm

 

[Guest]

--
Howard

You're welcome.


The way you have it set up now is the preferred way. Having multiple users
using the same frontend will lead to corruption. If you are asking this
because you face updating all 35 users with a new/modified frontend, you'll
want to look at a way to automate this. You could use a simple batch file
or look at Tony Toews' AutoFE Updater at
http://www.granite.ab.ca/access/autofe.htm


--
Joan Wild
Microsoft Access MVP

Joan,

That's why I'm asking! Thanks very much for the info.

Howard