Friday, December 18, 2009

The expression you entered refers to an object that is closed or doesn't exist ms access 2007 table open query

Sometimes when trying to open table or query in Micosoft access the users may receive the following error

The expression you entered refers to an object that is closed or doesn't exist

The reason for this error is the name of the table or query conflicts with a form or report in the access database.

To resolve this issue find the form or report which causes conflict then rename it.

Thursday, December 3, 2009

Can't create necessary temporary file (Error 322)

Can't create necessary temporary file (Error 322)

Sometimes the following error message will come

Can't create necessary temporary file (Error 322)


I got this error when i tried to create exe. Here i am going to explain the

reasons and best possible ways to avoid this error


Reasons

The temp directory is full

The TEMP environment variable specifies an invalid or read-only drive or

directory.


Actions To Be Taken

Delete files from the full drive or specify a different drive in the TEMP

environment variable.


Specify a valid drive for the TEMP environment variable or remove the read-only

restriction from the currently specified drive or directory.

Type Mismatch error vba,vb,Ms-access

Type mismatch (Error 13)


Visual Basic is able to convert and coerce many values to accomplish data type assignments that weren't possible in earlier versions. However, this error can still occur and has the following causes and solutions:

The variable or property isn't of the correct type. For example, a variable that requires an integer value can't accept a string value unless the whole string can be recognized as an integer.
Try to make assignments only between compatible data types. For example, an Integer can always be assigned to a Long, a Single can always be assigned to a Double, and any type (except a user-defined type) can be assigned to a Variant.

An object was passed to a procedure that is expecting a single property or value.
Pass the appropriate single property or call a method appropriate to the object.

A module or project name was used where an expression was expected, for example:
Debug.Print MyModule
Specify an expression that can be displayed.

You attempted to mix traditional Basic error handling with Variant values having the Error subtype (10, vbError), for example:
Error CVErr(n)
To regenerate an error, you must map it to an intrinsic Visual Basic or a user-defined error, and then generate that error.

A CVErr value can't be converted to Date. For example:
MyVar = CDate(CVErr(9))
Use a Select Case statement or some similar construct to map the return of CVErr to such a value.

At run time, this error typically indicates that a Variant used in an expression has an incorrect subtype, or a Variant containing an array appears in a Print # statement.
To print arrays, create a loop that displays each element individually.

Out of memory (Error 7)

Out of memory (Error 7)
Specifics

More memory was required than is available, or a 64K segment boundary was encountered. This error has the following causes and solutions:

You have too many applications, documents, or source files open.
Close any unnecessary applications, documents, or source files that are open.

You have a module or procedure that's too large.
Break large modules or procedures into smaller ones. This doesn't save memory, but it can prevent hitting 64K segment boundaries.

You are running Microsoft Windows in standard mode.
Restart Microsoft Windows in enhanced mode.

You are running Microsoft Windows in enhanced mode, but have run out of virtual memory.
Increase virtual memory by freeing some disk space, or at least ensure that some space is available.

You have terminate-and-stay-resident programs running.
Eliminate terminate-and-stay-resident programs.

You have many device drivers loaded.
Eliminate unnecessary device drivers.

You have run out of space for Public variables.
Reduce the number of Public variables.

Invalid procedure call

Invalid procedure call

When i was doing access programming i got this error called

Invalid procedure call

Initially i was very surprised about this error and now i understood this is a very

simple error and no need for much thinking in solving this error. Anyway i will give

some points regarding the reasons for this error and ways to avoid this error

Reasons

An argument probably exceeds the range of permitted values. For example, the Sin

function can only accept values within a certain range. Positive arguments less than

2,147,483,648 are accepted, while 2,147,483,648 generates this error.

Check the ranges permitted for arguments.



This error can also occur if an attempt is made to call a procedure that isn't valid

on the current platform. For example, some procedures may only be valid for

Microsoft Windows, or for the Macintosh, and so on.

Check platform-specific information about the procedure.

Return without GoSub

Return without GoSub

i was an access programmer. Once i was getting the error saying that

"Return without GoSub". From the message itself everyone can understand the real

reason and solutions


Reason

You have a Return statement that can't be matched with a GoSub statement.

Solution

Make sure your GoSub statement wasn't inadvertently deleted.

Wednesday, December 2, 2009

Export Access table data to Excel


Export Access table data to Excel


Sometimes as part of programming you may need to export data from MS-Access to microsoft excel for that follow the simple steps below

1. Right click on the access table

2. Choose Export.

3. Save file dialog will appear

4. In that choose file type as excel and give filename


Export Arabic Data To Excel



If theire is any arabic of any other language data is in the access table then the

data exported will show as "??????????????" for that the best possible way is

1. Open the access table

2. Scroll down to the bottom

3. Click on the "*" below by pressing shift

4. Right click and select copy

4. Open a blank excel file

5. Paste the contents



HAPPY PROGRAMMING

PRAISE THE LORD