Newly Created tables

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Barbara Musante - 23 Feb 2006 20:23 GMT

I have a situation where I need to create a new table in the current sql
database in my access project and then use the contents of the table in other
parts of the project. It seems that the project cannot see the new table
unless I disconnect and re-connect the ADO connection. Is there another way
to do this?

thanks

Signature

Barbara Musante
Partner

Reply to this Message

Tom Ellison - 24 Feb 2006 10:12 GMT

Dear Barbara:

Your experience does not match mine. I am able to use a table immediately
after creating it, provided it is in a database to which I am connected.

Could you please share the detaila of how you are creating this table, how
you are subsequently addressing the table, and what specific error it is
generating? Perhaps someone will then see what is wrong.

Tom Ellison

>I have a situation where I need to create a new table in the current sql
> database in my access project and then use the contents of the table in
[quoted text clipped - 5 lines]
>
> thanks

Reply to this Message

Tom Ellison - 24 Feb 2006 10:32 GMT

for "detaila" please read "details"

Tom

> Dear Barbara:
>
[quoted text clipped - 16 lines]
>>
>> thanks

Reply to this Message

Barbara Musante - 24 Feb 2006 18:33 GMT

Hi Tom,

Thanks for the response. The way I create and use the table is this. I
first execute a stored procedure that creates the table using a select
.....into tblstorestatus. After that I attempted to do a docmd.transfertext
on this table to create a text file of the information. Unless I do a
application.currentproject.closeconnection followed by a
application.currentproject.openconnection, the transfertext operation gets an
error that it cannot find the object.

I hope that this explains the situation and also hope that you can help.

Signature

Barbara Musante
Partner

> Dear Barbara:
>
[quoted text clipped - 16 lines]
> >
> > thanks

Reply to this Message

Sylvain Lafontaine - 24 Feb 2006 19:49 GMT

Maybe making a call to Application.RefreshDatabaseWindow will solve this.
There is also the possibility of a timing problem: if you make the call from
ADP too fast after the creation of the new table, you won't still see it
because SQL-Server didn't have the time to finalize the operation; so you
may have to introduce a short delay between these two operations.

See the post from Ron Hinds on
http://groups.google.ca/group/microsoft.public.access.adp.sqlserver/browse_frm/t
hread/4e723da0f9add729/938eac123effb43c?q=RefreshDatabaseWindow&rnum=3#938eac123
effb43c
to see how to call the Sleep() function from ADP (however, I don't know if
this will work for you).

Signature

Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF

> Hi Tom,
>
[quoted text clipped - 34 lines]
>> >
>> > thanks

Reply to this Message

Barbara Musante - 24 Feb 2006 20:15 GMT

Thank you for the suggestion. I think that this will work. I am assuming
that you can use the refresh command even in an .ade.

Thanks again.

Signature

Barbara Musante
Partner

> Maybe making a call to Application.RefreshDatabaseWindow will solve this.
> There is also the possibility of a timing problem: if you make the call from
[quoted text clipped - 45 lines]
> >> >
> >> > thanks

Reply to this Message