Syntax Error

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

Guest

OMG Please help me! I have been staring at this for days now and I am about
to throw it out the window!

I have created my little tables. NONE of them have any default values or
even anything tricky like functions or "specifics". I am trying to work on a
form however this little program keeps coming up with the error "Syntax Error
in FROM clause".... Great....no references....no how to figure out what the
heck its problem is.

Granted I am new to this and I bought and Access for Dummies book....and
right now its winning! How can I have a "FROM Clause" error when i haven't
put in any #$&@&#*&* clauses??? Am I missing something (dripping with
sarcasm)...anyways I need to have a functioning form and database ready this
week for my boss and at this point....I got some tables and that is about it!

If anyone can help me I would appreciate it muchly! I am going to go have a
beer now!

Kara
 
Well, unfortunately none of us will be able to help you unless we know what
your SQL statement looks like!
 
Doug:

Ummm....If i go into the "View" area....it does not appear that I have
anything related to SQL at all....as in that is not listed as a view option,
nor is any Pivot Tables or such....hmmm I am guessing maybe there should be
from your last post...ha ha ha! Please just shoot me now! Thanks!
 
Kara said:
Doug:

Ummm....If i go into the "View" area....it does not appear that I have
anything related to SQL at all....as in that is not listed as a view
option, nor is any Pivot Tables or such....hmmm I am guessing maybe
there should be from your last post...ha ha ha! Please just shoot me
now! Thanks!
Click to expand...

If you created a form with the wizard then you had to tell the wizard which
table to use. The wizard would then have constructed a SQL statement based on
that table and you will find that SQL statement in the RecordSource property of
the form in design view.
 
Ohhh Rick I feel one step closer thanks! LOL

K...here is my SQL thingy (not the technical term I know ....)
SELECT
FROM (([Drop Down Lists] INNER JOIN (Customers INNER JOIN [Inventory Used]
ON ([Inventory Used].[Customer ID] = Customers.[Customer ID]) AND
(Customers.[Invoice #] = [Inventory Used].[Invoice #])) ON ([Drop Down
Lists].ID = [Inventory Used].ID) AND ([Drop Down Lists].[Carpentry Hours] =
[Inventory Used].[Carpentry Hours])) INNER JOIN [Job Information] ON ([Drop
Down Lists].ID = [Job Information].ID) AND ([Job Information].Township =
[Inventory Used].Township) AND (Customers.Township = [Job
Information].Township)) INNER JOIN Employee ON Customers.[Order ID] =
Employee.[Employee ID];

Now what? LOL

Kara
 
Kara said:
Ohhh Rick I feel one step closer thanks! LOL

K...here is my SQL thingy (not the technical term I know ....)
SELECT
FROM (([Drop Down Lists] INNER JOIN (Customers INNER JOIN [Inventory
Used] ON ([Inventory Used].[Customer ID] = Customers.[Customer ID])
AND (Customers.[Invoice #] = [Inventory Used].[Invoice #])) ON ([Drop
Down Lists].ID = [Inventory Used].ID) AND ([Drop Down
Lists].[Carpentry Hours] = [Inventory Used].[Carpentry Hours])) INNER
JOIN [Job Information] ON ([Drop Down Lists].ID = [Job
Information].ID) AND ([Job Information].Township = [Inventory
Used].Township) AND (Customers.Township = [Job
Information].Township)) INNER JOIN Employee ON Customers.[Order ID] =
Employee.[Employee ID];

Now what? LOL
Click to expand...

That is an invalid statement (hence your error). There should be field names
listed after "SELECT" and before "FROM". If you are familiar with building
queries I would delete the entire statement and then click on the build button
[...] to the right. That wil bring up the query builder which you can use to
create the query over again properly. If you are not familiar with building
queries I would rebuild the form over agaon from scratch using the wizard.

By the way, a query using that many tables will most likely be Read-Only so if
you wanted the form to be able to edit records there's a good chance that it
will not work.
 
5 Tables is too many? should I break it down into 2....its just that it
would leave me needing like 50 fields in order to enter all the fields I
need. I am thinking I should just hire someone to do this....cause I just
don't get it!

Thanks for your help....looks like I will start from scratch.

Kara


Rick Brandt said:
Kara said:
Ohhh Rick I feel one step closer thanks! LOL

K...here is my SQL thingy (not the technical term I know ....)
SELECT
FROM (([Drop Down Lists] INNER JOIN (Customers INNER JOIN [Inventory
Used] ON ([Inventory Used].[Customer ID] = Customers.[Customer ID])
AND (Customers.[Invoice #] = [Inventory Used].[Invoice #])) ON ([Drop
Down Lists].ID = [Inventory Used].ID) AND ([Drop Down
Lists].[Carpentry Hours] = [Inventory Used].[Carpentry Hours])) INNER
JOIN [Job Information] ON ([Drop Down Lists].ID = [Job
Information].ID) AND ([Job Information].Township = [Inventory
Used].Township) AND (Customers.Township = [Job
Information].Township)) INNER JOIN Employee ON Customers.[Order ID] =
Employee.[Employee ID];

Now what? LOL
Click to expand...

That is an invalid statement (hence your error). There should be field names
listed after "SELECT" and before "FROM". If you are familiar with building
queries I would delete the entire statement and then click on the build button
[...] to the right. That wil bring up the query builder which you can use to
create the query over again properly. If you are not familiar with building
queries I would rebuild the form over agaon from scratch using the wizard.

By the way, a query using that many tables will most likely be Read-Only so if
you wanted the form to be able to edit records there's a good chance that it
will not work.
Click to expand...
 
Kara said:
5 Tables is too many? should I break it down into 2....its just that
it would leave me needing like 50 fields in order to enter all the
fields I need. I am thinking I should just hire someone to do
this....cause I just don't get it!

Thanks for your help....looks like I will start from scratch.
Click to expand...

The number of fields does not determine how many tables you should have.
You should have a table "per-entity" being described by the data. To
properly describe your entities and their relationships might very well
require many tables. Where you are going wrong is thinking then that a
single form can then be used to add/enter records.
 
Back
Top