By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,795 Members | 1,666 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,795 IT Pros & Developers. It's quick & easy.

Not a legal object name - huh?

P: n/a
Access 2k FE - SQL Server 2k BE

I've been asked to do some work on this Access application. It was an
Access<->Access app., but I've upsized the BE to SQL Server 2k. As far
as I can see it runs fine. It compiles fine.

I'm trying to add it to SourceSafe (Version 6c) and then check it out.
FYI the name of the application is eFIMS, and the name of the file is
eFIMS.mdb

It seems to add the project to SourceSafe with no trouble.

Now I wish to get a working copy from SourceSafe, so I go to Tools,
SourceSafe, Create Database from SourceSafe Project

Select the eFIMS project and choose a working folder.

While SourceSafe is adding the various files it suddenly stops and
tells me:

"Not a legal object name: FIMS.mdb"

If I click "Ok" to that I get a further error message:

"Failed to import file C:\Project\eFIMS\eFIMS.scc\eFIMS.acb into
Microsoft Access".

Click OK and it tells me that the operation completed successfully.

Only it didn't. If I open a code module and try to compile, I get a
"variable not defined" error.

If I re-open a working copy (prior to adding to SS), locate the
variable that apparently isn't defined, and right-click and go to
"Definitiion" I get the message:

"Cannot jump to "Actual End Time" because it is in the library
'C:\Project\eFIMS\eFIMS.mdb' which is not currently referenced"

Can ANYONE tell me what the blue blazes is going on?

TIA

Edward

Sep 22 '06 #1
Share this Question
Share on Google+
6 Replies


P: n/a
I have had problems with sourcesafe also, and I heard that other people
have too. I switched to subversion and have not had any issues to speak
of. You might give that a try.

Rich

*** Sent via Developersdex http://www.developersdex.com ***
Sep 22 '06 #2

P: n/a

<te********@hotmail.comwrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...
Access 2k FE - SQL Server 2k BE

I've been asked to do some work on this Access application. It was an
Access<->Access app., but I've upsized the BE to SQL Server 2k. As far
as I can see it runs fine. It compiles fine.

I'm trying to add it to SourceSafe (Version 6c) and then check it out.
FYI the name of the application is eFIMS, and the name of the file is
eFIMS.mdb

It seems to add the project to SourceSafe with no trouble.

Now I wish to get a working copy from SourceSafe, so I go to Tools,
SourceSafe, Create Database from SourceSafe Project

Select the eFIMS project and choose a working folder.

While SourceSafe is adding the various files it suddenly stops and
tells me:

"Not a legal object name: FIMS.mdb"

If I click "Ok" to that I get a further error message:

"Failed to import file C:\Project\eFIMS\eFIMS.scc\eFIMS.acb into
Microsoft Access".

Click OK and it tells me that the operation completed successfully.

Only it didn't. If I open a code module and try to compile, I get a
"variable not defined" error.

If I re-open a working copy (prior to adding to SS), locate the
variable that apparently isn't defined, and right-click and go to
"Definitiion" I get the message:

"Cannot jump to "Actual End Time" because it is in the library
'C:\Project\eFIMS\eFIMS.mdb' which is not currently referenced"

Can ANYONE tell me what the blue blazes is going on?

TIA

Edward
Wild shot in the dark.

Try creating under Options: File Types Tab, a File Group for this project,
and make sure to list *.mdb as a binary file.

-ralph
Sep 22 '06 #3

P: n/a
On 22 Sep 2006 07:47:14 -0700, te********@hotmail.com wrote:

Before you use SourceSafe integration with Access at the object level,
it is good to read up on how to use it, and its limitations.
For our company, we consider the limitations too severe, and only
check in entire MDB files.

-Tom.

>Access 2k FE - SQL Server 2k BE

I've been asked to do some work on this Access application. It was an
Access<->Access app., but I've upsized the BE to SQL Server 2k. As far
as I can see it runs fine. It compiles fine.

I'm trying to add it to SourceSafe (Version 6c) and then check it out.
FYI the name of the application is eFIMS, and the name of the file is
eFIMS.mdb

It seems to add the project to SourceSafe with no trouble.

Now I wish to get a working copy from SourceSafe, so I go to Tools,
SourceSafe, Create Database from SourceSafe Project

Select the eFIMS project and choose a working folder.

While SourceSafe is adding the various files it suddenly stops and
tells me:

"Not a legal object name: FIMS.mdb"

If I click "Ok" to that I get a further error message:

"Failed to import file C:\Project\eFIMS\eFIMS.scc\eFIMS.acb into
Microsoft Access".

Click OK and it tells me that the operation completed successfully.

Only it didn't. If I open a code module and try to compile, I get a
"variable not defined" error.

If I re-open a working copy (prior to adding to SS), locate the
variable that apparently isn't defined, and right-click and go to
"Definitiion" I get the message:

"Cannot jump to "Actual End Time" because it is in the library
'C:\Project\eFIMS\eFIMS.mdb' which is not currently referenced"

Can ANYONE tell me what the blue blazes is going on?

TIA

Edward
Sep 23 '06 #4

P: n/a

Tom van Stiphout wrote:
On 22 Sep 2006 07:47:14 -0700, te********@hotmail.com wrote:

Before you use SourceSafe integration with Access at the object level,
it is good to read up on how to use it, and its limitations.
For our company, we consider the limitations too severe, and only
check in entire MDB files.

-Tom.
We've been using SourceSafe integration for Access for nearly ten
years, and this is the first time we've had this sort of problem.

Edward

Sep 25 '06 #5

P: n/a

te********@hotmail.com wrote:
Access 2k FE - SQL Server 2k BE
[...]

Sorted.

The problem was the Properties page for the database.

Right-click on the title bar of the Database window.

In the Summary tab is a Title field. This didn't match the name of the
file:

FILENAME: e-fims.mdb
TITLE: FIMS.mdb

When I changed the title, all was rosy.

Edward

Sep 25 '06 #6

P: n/a

<te********@hotmail.comwrote in message
news:11**********************@i3g2000cwc.googlegro ups.com...
>
te********@hotmail.com wrote:
Access 2k FE - SQL Server 2k BE
[...]

Sorted.

The problem was the Properties page for the database.

Right-click on the title bar of the Database window.

In the Summary tab is a Title field. This didn't match the name of the
file:

FILENAME: e-fims.mdb
TITLE: FIMS.mdb

When I changed the title, all was rosy.

Edward
Thanks for the feedback. I have been bitten by that myself occasionally, but
never thought of it - I guess one tends to blank out bad memories. <g>

-ralph
Sep 25 '06 #7

This discussion thread is closed

Replies have been disabled for this discussion.