text file specification

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a database that displays student data, student pictures and student
schedules. I moved my tblSchedules from an imported file in the back end of
the database to a linked file in the front end of the database. Everything
still works fine except when I add my frmMainForm as a startup form I get the
message "The text file specification 'Schedule Link Specification' does not
exist. You cannot import, export, or link using the specification." What am
I doing wrong?

Thank in advance for any help on this one.
 
Hi Doug,

It sounds from what you say that everything (including frmMainForm)
works normally unless you set frmMainForm as the startup form, but that
if frmMainForm is the startup form you're getting this error message as
the form loads. But I don't really understand what you mean by this:
moved my tblSchedules from an imported file in the back end
of the database to a linked file in the front end of the database.

Do you mean tblSchedules is now a linked table connected to a text file?

If you search http:/groups.google.com for

group:microsoft.public.access.* "text file specification" "does not
exist"

you'll find some previous experiences with this error, which doesn't
have a single obvious cause. Things to try are

1) Make quite certain that the import specification matches the text
file exactly (e.g. has the correct number of fields). Some people have
suggested that it's best not to use spaces in the specification name
(e.g. "ScheduleLinkSpec"

2) Identify what controls or procedures in frmMainForm use tblSchedules.
Knowing this could identify the source of the problem.

3) Conceivably there's a timing issue, in which something in frmMainForm
is trying to use the linked table before the import specification is
available. If this is the problem you can probably work round it by
creating a separate startup form ("splash form") that simply
a) loads itself
b) waits a second or two (using its built-in TimerInterval)
c) in its OnTimer event procedure, launches frmMainForm and closes
itself.
 
Back
Top